You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Bilibili playback permanently hangs on timestamp gaps without requesting new chunks (MSE gap deadlock) #361
Occasionally during continuous playback of a Bilibili video (e.g. BV1fKaz6WEnb), playback suddenly freezes at a specific timestamp (e.g. at 19:28) and hangs indefinitely with a loading spinner. It never recovers on its own unless the user manually seeks forward on the progress bar. Checking the server logs during the multi-minute freeze, the proxy and network were completely normal, but the browser had completely stopped requesting media chunks (/api/media/... requests dropped to zero). It looks like an MSE gap deadlock: a micro timestamp/PTS gap causes the <video> element to stall. Because playback halts, the forward buffer is never consumed, so dash.js thinks the buffer is still full and refuses to fetch the next segment, creating an infinite stall until an explicit seek clears the pipeline.
Steps to reproduce
Open a longer Bilibili video (e.g. https://www.bilibili.com/video/BV1fKaz6WEnb).
Let it play continuously through minute 19.
At 19:28, the video suddenly freezes while the loading indicator spins indefinitely.
Notice that no media network activity happens during the freeze (chunk requests drop to zero).
Drag the progress bar past 19:28 (e.g. to 20:00) -> chunk requests instantly resume and playback continues normally.
1.13.0 keeps dash.js jumping over small buffer holes after a manual quality change, which could freeze playback for good. Could you check if BV1fKaz6WEnb still stops at 19:28? (◕ᴗ◕✿)
Activity
Priveetee commentedon Oct 30, 2026
1.13.0 keeps dash.js jumping over small buffer holes after a manual quality change, which could freeze playback for good. Could you check if
BV1fKaz6WEnbstill stops at 19:28? (◕ᴗ◕✿)Aquarius-Situla commentedon Oct 31, 2026
Thx for the fix :D