From 7a02f3b21f56977b9f2551da5ee1e4928d2030e1 Mon Sep 17 00:00:00 2001
From: nyanmisaka <nst799610810@gmail.com>
Date: Fri, 27 Jun 2025 12:29:09 +0800
Subject: [PATCH] Set maxMaxBufferLength to avoid bufferAppendError on Chrome
 138

```
HLS Error: Type: mediaError Details: bufferAppendError Fatal: true
```

It seems that the default buffer eviction behavior has changed in
Chrome 138, so the default maxMaxBufferLength from hls.js don't apply.

Signed-off-by: nyanmisaka <nst799610810@gmail.com>
---
 src/plugins/htmlVideoPlayer/plugin.js | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/plugins/htmlVideoPlayer/plugin.js b/src/plugins/htmlVideoPlayer/plugin.js
index 541a13e91e..b647c5dcb3 100644
--- a/src/plugins/htmlVideoPlayer/plugin.js
+++ b/src/plugins/htmlVideoPlayer/plugin.js
@@ -453,6 +453,7 @@ export class HtmlVideoPlayer {
                     startPosition: options.playerStartPositionTicks / 10000000,
                     manifestLoadingTimeOut: 20000,
                     maxBufferLength: maxBufferLength,
+                    maxMaxBufferLength: maxBufferLength,
                     videoPreference: { preferHDR: true },
                     xhrSetup(xhr) {
                         xhr.withCredentials = includeCorsCredentials;