Bugzilla

I got a profiled result from an anonymous user for the same buffering issue. By debugging it, the problem seems caused by incorrect audio clock. In this profiled result, there are two main section where the playback should be started, the first one is around `22-29s` and another one is after `50s`.

Let's check the first section. That part loaded a Youtube video, and at `28.944s` the MDSM [started playback](https://share.firefox.dev/3Vj3gZa). At `29.065s`, we already had 11 video frames in [MDSM's video queue](https://share.firefox.dev/3yWyoWF).  However, the playback wasn't started properly, the video should be still stuck. When checking the audio clock, I found that [the audio clock wasn't forward at all](https://share.firefox.dev/3VDPPnQ). We can observe same situation at `50.848s` where user seems seeking video to another position, but the playback still stuck because the audio clock stuck as well.

Paul, Matthew, do you have any thought about that? I suspect the problem might be related with either cubeb or audio IPC. Thanks!

I got a profiled result from an anonymous user for the same buffering issue. By debugging it, the problem seems caused by incorrect audio clock. In this profiled result, there are two main section where the playback should be started, the first one is around `22-29s` and another one is after `50s`.

Let's check the first section. That part loaded a Youtube video, and at `28.944s` the MDSM [started playback](https://share.firefox.dev/3Vj3gZa). At `29.065s`, we already had 11 video frames in [MDSM's video queue](https://share.firefox.dev/3yWyoWF).  However, the playback wasn't started properly, the video should be still stuck. When checking the audio clock, I found that [the audio clock wasn't forward at all](https://share.firefox.dev/3VDPPnQ). We can observe same situation at `50.848s` where user seems seeking video to another position, but the playback still stuck because the audio clock stuck as well.

Paul, Matthew, do you have any thought about that? I suspect that the one of the possible root causes of this problem is related with either cubeb or audio IPC. Thanks!