UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Steps to reproduce the problem:
1. Make an HTMLVideoElement.
2. Connect it to a MediaSource with a SourceBuffer attached to a real-time stream.
3. Attempt to keep video playback at the live edge by seeking to slightly before the end of the buffer on timeupdate, if the currentTime is too far behind.

What is the expected behavior?
Playback remains smooth, maybe occasionally jumping if it's fallen too far behind for whatever reason.

What went wrong?
Our application requires extremely low latency in video processing and playback, so we have a video element connected to a media source set up to seek to a point close to the end of the buffer if it's fallen behind too far upon timeupdate. On Firefox, this works fine. Latency remains low and the stream runs smoothly. On Chromium and derivatives, however, we notice the dropped frame count steadily increasing with constant visual hitching. If we set it to try to catch up less often, we see fewer dropped frames but latency increases to about 100ms at minimum, even though we're seeking to a point 7ms behind the end of the buffer.

We're using a real-time stream here, so data is coming in at exactly the rate of playback. In practice, the stream would occasionally fall behind. Hence, the synchronization code.

I can't include a complete test case, but I will attach a copy of the timeupdate event in question from our MediaManager class.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 64.0.3282.186  Channel: n/a
OS Version: 10.0
Flash Version:
 

Deleted: timeupdate.ts 1.0 KB

timeupdate.ts 1.0 KB Download