[chromium-dev] HTML5 video with Preload="metadata" hangs in chrome

[Anand Tekaday]

Hi,

We are running in an issue where our MP4 html5 videos are getting stuck
after first frame. In this case chrome does not seem to be buffering video
beyond the first frame it got as a response to metadata call for the video.

Looking at network traces, it looks like chrome starts a connection with a
range header set to "0-" but terminates the connection after few hundred kb
data is downloaded and starts a new connection with different range header
eg. "300000-" to load rest of the video when video is played.

Here the first request does not always download the same amount of data and
as a result when less data is downloaded for the first request, the video
does not play.

This issue does not happen if we use preload="none" or preload="auto". Also
this issue does not happen on any other browser other than chrome (yes we
have tried multiple versions of chrome)

Is this a known issue?
What could potentially get chrome into this state? (we checked our mp4
files for corrupt metadata but everything looks fine there).

[Philip Jägenstedt]

I don't know if it's a known issue, but if you have a way to reliably
reproduce it, please file a bug at https://crbug.com/new and hopefully
it'll get triaged.

Post by Anand Tekaday
Hi,
We are running in an issue where our MP4 html5 videos are getting stuck
after first frame. In this case chrome does not seem to be buffering video
beyond the first frame it got as a response to metadata call for the video.
Looking at network traces, it looks like chrome starts a connection with a
range header set to "0-" but terminates the connection after few hundred kb
data is downloaded and starts a new connection with different range header
eg. "300000-" to load rest of the video when video is played.
Here the first request does not always download the same amount of data
and as a result when less data is downloaded for the first request, the
video does not play.
This issue does not happen if we use preload="none" or preload="auto".
Also this issue does not happen on any other browser other than chrome (yes
we have tried multiple versions of chrome)
Is this a known issue?
What could potentially get chrome into this state? (we checked our mp4
files for corrupt metadata but everything looks fine there).
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev