DASH video corruption seemingly at random

[Discookie]

I've been watching DASH videos, and this is the second time I've had a corrupted video like this one.

There's sometimes a full-screen color change, but otherwise only the top few rows change.

It looks like the video files are somehow misaligned? It might come from proxying dropping a bit of data, or from a bug in the DASH player. A refresh fixes it, and usually after a minute or so it fixes itself.

I couldn't find a way to reproduce this issue reliably, but here's the link anyways:
https://invidio.us/watch?v=-LytcXun4hU

I've had this issue on 2 separate machines, on Waterfox 56.2.3 on Win10/AMD and a Chromium 69.0 on Win8.1/Nvidia.

[omarroth]

Does it reliably happen ~x seconds into the video? It might be the case that Invidious is generating a bad manifest that results in an incorrect offset like what appears to be encountered. Does devtools show any errors?

Currently, Invidious uses videojs/videojs-contrib-dash, because videojs/http-streaming does not yet support features that Invidious uses in its manifests. I suspect the issue is in the player since it disappears after a refresh, and I think this issue will likely go away after switching to http-streaming.

[Discookie]

Found a semi-reliable way to reproduce it, and it looks more like a player issue:
Simply jump forward with the arrows to the very end of the buffer.
If you get unlucky, your video will corrupt the same way.

dash.mediaplayer.min.js throws this warning:

[496953][Stream] onBufferingCompleted - can't trigger STREAM_BUFFERING_COMPLETED because streamProcessor audio is not buffering completed

The audio and the corrupted video continued without interruption.

A potential fix would be to stop the video and wait for buffer ~1s before the end of the buffer?

[omarroth]

Switched over to http-streaming with 075adb4 which should hopefully resolve this issue.

[Discookie]

Encountered it the very first time I tried to switch resolutions with the new source selector :/

Although it's starting to smell more like hardware issues, because Streamable's being corrupted on the AMD machine too. GPU/decode stress testing didn't report anything so far, but I'll keep testing.

[github-actions]

This issue has been automatically marked as stale and will be closed in 30 days because it has not had recent activity and is much likely outdated. If you think this issue is still relevant and applicable, you just have to post a comment and it will be unmarked.