Several GET requests for <video>

[Patrick Stinson]

I am looping video on a video element at timed intervals by calling
pause(), setting currentTime = 0, and then after a specified time
interval calling play(). It seems that chrome is making a GET for the
video url every time I call pause() and set currentTime = 0. Is it
possible to tell chrome to simply buffer the video data completely
thereby preventing the subsequent requests? All of these are only
coming over a local network so I'm not worried about bandwidth or
buffer times. Preload="true" doesn't seem to help. I am on windows.

The reason I am asking is that after a while the video and entire page
seems to freeze, and I am thinking that this is something to do with
the known bugs of the byte range functionality. Even refreshing the
page doesn't work, and killing the process in Task Manager kills two
of the three leaving one dangling. I have a hunch that these extra
requests are somehow leading to this. Not sure what else to try.

I am running chrome with --disable-byte-range-support and --kiosk
command line options

Thanks!

[Alessandro Nunes]

Hello Patrick,

I'm getting a similar problem with a video. I jump to 5 different points of the video, playing only 3 seconds of each fragment.

Checking the buffered attribute I can see that exists buffer for each fragment, so I supposedly can use this buffer again.

What happens is: first fragment buffer is used, middle fragments download again (I can see on the network console), and the last one use the buffer.

Clean cache, reload. Same result.

Anybody could explain that? Why the buffer is not being used?

Thanks!