Re: Issue 111281 in chromium: HTML5 audio files stop buffering

[chro...@googlecode.com]

Updates:
Labels: norepro Action-FeedbackNeeded

Comment #2 on issue 111281 by imas...@chromium.org: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #3 on issue 111281 by asadov...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

FWIW, I am seeing a similar issue with Google Dictionary Chrome extension
pronunciations. Often times when I click the pronunciation icon, the HTML5
audio stutters. This only started happening recently.
Feel free to contact me internally (sadovsky@) for more information.

[chro...@googlecode.com]

Comment #10 on issue 111281 by y.hoogst...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I'm having a similar problem, although my latencies seem to be smaller (10
- 100 milliseconds) and more frequent (about every 10 sec).

These are my specs:
17.0.963.65 (Developer Build 124586 Linux) Built on Ubuntu 11.10, running
on LinuxMint 12

I found these latency on my own personal server but it also occurs on the
given website above.

It cannot have to do anything with my soundcard settings because other
browsers play the music properly.

I might have a clue where this error is pointing to, that is using "Partial
Content" headers from the server.

[chro...@googlecode.com]

Comment #19 on issue 111281 by kirb...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I am having the same fail-to-buffer issue. Audio starts to play and
somewhere around 7-10 mins in to an hour long MP3, it will just stop with
the error that it failed to load the resource.

This is using Version 21.0.1180.57 on OSX Mountain Lion.

[chro...@googlecode.com]

Comment #20 on issue 111281 by came...@kera.io: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I'm also having the same issue as c#19. I traced out events and it seems
like the last event that dispatches is a 'stalled' event and the audio
element moves into NETWORK_LOADING state.

Version 23.0.1232.0 canary on OSX Mountain Lion w Macbook Pro Retina Display

[chro...@googlecode.com]

Comment #21 on issue 111281 by came...@kera.io: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

It seems like the workaround for this is to play and then immediately pause
the audio. This forces the entire file to buffer instead of 'progressively
buffering' as needed.

Admittedly this doesn't work for use cases where the entire audio file is
not consumed but it works for my purposes.

Any idea of when this is going to be looked at?

[chro...@googlecode.com]

Comment #22 on issue 111281 by picoliga...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Okay, I think I've figured out a likely (but not certain) cause:

Chrome has a limit of 6 open connections to a single host. If you create,
say, 9 audio elements on a page, then only 6 will buffer at a time. I
actually discovered several issues in this process:

1. Every html5 audio file is listed twice in the inspector. Demo:
https://wli.me/html5audio/double_buffer.html (see attached screenshot for a
quick reference). The src is just <audio src="sample1.mp3"
controls="controls"></audio>.

2. In the above scenario with 9 audio files, the other 3 audio files will
actually _never_ buffer. Demo: https://wli.me/html5audio/music.html (make
sure to clear your cache). You can look at the inspector (or even just the
controls UI), and notice that the first 6 buffer 2.35MB each, and then
stop, but the other 3 never buffer anything at all. Each file is 11M
(symlinked on the server to be the same source file, but it transfers once
per unique URI). Please see the attached image (limit6.png).

3. At some time in the future, the original connections will time out or
otherwise get cut out. This results in connection spots being freed, but
the original files are now not fully buffered, and when you play them,
they do not complete the song. This problem is difficult to reproduce, but
it has happened quite a few times to me.

4. There is no way to actually buffer the entire file to free up connection
slots. Right now, it only gets 2MB at a time, and then waits/blocks until
the file is seeked. Even playing the file will not buffer the full file -
you have to seek to either a point past the buffered portion, or "close
enough" to the limit of the buffered portion. preload="auto" is supposed to
buffer the entire file, but in practice it does not do that. Reference:
http://www.w3.org/TR/html-markup/audio.html#audio.attrs.preload

Hope this helps! Again, feel free to contact me over chat internally if you
need help or more details. I'm the original reporter of this bug, but I'm
on my personal account trying to debug this on the weekend :).

Attachments:
audio_double_buffer.png 94.1 KB
limit6.png 209 KB

[chro...@googlecode.com]

Comment #23 on issue 111281 by picoliga...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Forgot to mention, back in 2010 and 2011, Chrome actually fully buffered
the entire file instead of processing in 2MB chunks and then waiting. This
behavior change is likely the biggest cause of the regressions seen in the
thread - I would love to see this behavior reverted if possible.

[chro...@googlecode.com]

Comment #24 on issue 111281 by came...@kera.io: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

So my workaround listed above doesn't seem to work. Even though the audio
appears to buffer completely after pausing, if you play it will
still 'stall'. Anyone else find a workaround?

[chro...@googlecode.com]

Comment #25 on issue 111281 by ZakK...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I can report that this is also happening for me, and has been for several
versions. Currently running Version 23.0.1271.1 dev on Mountain Lion. Most
notably occurs when playing audio on 5by5.tv, which is one audio player per
page.

[chro...@googlecode.com]

Comment #26 on issue 111281 by kael.fis...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Very reproducible; multiple Windows 7 machines; Chrome version:
22.0.1229.79 m; playing long (30-60') audio file; sound stops ;buffer bar
frozen at current position; Control unresponsive to clicking; reloading
page enables control.

Work around: open page using IE Tab extension (http://goo.gl/2ANyg).

[chro...@googlecode.com]

Comment #27 on issue 111281 by rtenn...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I'm experiencing a similar problem with the audio element. This problem
doesn't occur on other browsers (IE9-10, Firefox 17, Safari 6). Chrome
makes an open ended byte range request and shows about ~2MB of data loaded
in the network panel. On the server side, we see about 4MB of data written
for that request out of 8 in my example, then the connection is closed by
the client. When you click play in Chrome, it will play the data it has
dowloaded then stop. No further requests are made by Chrome to the server
to load more data. Basically, it appears that it only plays what it
initially buffers on page load. When it reaches the end of the buffered
data, it will send an error event with the code MEDIA_ERR_NETWORK having
made no attempt to load more data.

[chro...@googlecode.com]

Comment #31 on issue 111281 by al.iii...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

The same issue

[chro...@googlecode.com]

Comment #32 on issue 111281 by silver...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

same issue here Chrome Version 24.0.1312.52

[chro...@googlecode.com]

Comment #35 on issue 111281 by kael.fis...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I had this problem, but after updating Chrome, it's now fixed.

Google Chrome: 24.0.1312.52 m
OS: Windows 7 64-bit

[chro...@googlecode.com]

Comment #36 on issue 111281 by bcl...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Faced this problem too. And thanks #22 for the investigation. Indeed it
looks like changed loading scheme is the culprit.

Holding opened connections to an audio stream may be harmful in some cases.
For example when the stream is generated somehow by a server. Server may
just decide that the client timed out.

I vote for download-and-cache as fast as possible. And at the same time
please do not break free seek in mp3 files!

P.S. HTML5 is still so far from being reliable...

[chro...@googlecode.com]

Comment #37 on issue 111281 by samuel.v...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Not fixed here. Win8 64 24.0.1312.57 m.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #40 on issue 111281 by rishi629...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I am facing a similar issue.....my application requires the audio to be
completely loaded before playing...if the audio is more than 2 MB...the
audio stops loading after 2 MB and never loads again....is there any
workaround for this issue.My Chrome version is 26.0.1410.43

[chro...@googlecode.com]

Comment #42 on issue 111281 by salik1...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

The same problem here. If the file is too large and it stops buffering
after a while. Does the preload="auto" attribute works, to buffer the
entire file before playing it?

[chro...@googlecode.com]

Comment #45 on issue 111281 by dan.nutt...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Same issue here. Streams work fine with a Flash audio player, not with a
HTML5.

[chro...@googlecode.com]

Comment #46 on issue 111281 by Cheddes...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Wow after one year and a half the bug is still alive, on version
29.0.1547.66 m, i try to send different header but nothing work.

[chro...@googlecode.com]

Comment #47 on issue 111281 by morris.j...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Same here - I can reproduce the error. If somebody needs a reproducable
test page I can provide one. Please contact me.

[chro...@googlecode.com]

Comment #48 on issue 111281 by goo...@cayzland.de: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Same here. Tested on different devices and internet connections. Only
Chrome has this Problem. The same problem since years and there is still no
reaction.

[chro...@googlecode.com]

Comment #49 on issue 111281 by kie....@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

this has been an issue for me for at least a year. i really hope this gets
fixed soon. this site uses audioboo which regularly triggers the issue:
http://www.kiddnation.com/category/kpod/

[chro...@googlecode.com]

Comment #50 on issue 111281 by fabiopen...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

You use.
<audio src="" preload="none" autoplay="true" />

Remove autoplay.
<audio src="" preload="none" />

[chro...@googlecode.com]

Comment #51 on issue 111281 by elmo...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Happening for us here. Our MP3 files are smaller than 2MB, but length seems
to matter. Files longer than 30-40 seconds cause subsequent requests of any
resources to lock Chrome.

Win 7-64, Chrome 31.0.1650.57 m

Does not happen in other browsers.

[chro...@googlecode.com]

Comment #52 on issue 111281 by innervib...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Mac OS
Chrome 31
Safari latest
FF latest

Still an issue here as well. Almost *two years*. Post more than 10 minutes
of audio on a page and Chrome locks. Totally unacceptable for a modern
browser. Google please respond.

[chro...@googlecode.com]

Comment #59 on issue 111281 by sche...@chromium.org: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

dave: do you have URLs to share? how long are these audio files that you're
listening to?

I listen to music all day via HTML5 audio and haven't hit these issues...
but I'd love to examine any scenarios where you can reliably encounter
these issues.

[chro...@googlecode.com]

Comment #60 on issue 111281 by elmo...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Our experience is that we can request a URL that points to an MP3 file. The
MP3 file plays to the end. If we reload the URL after the audio completes,
the browser locks up. It is easily reproducable. Unfortunately, I cannot
give a URL because it belongs to a client.

[chro...@googlecode.com]

Comment #61 on issue 111281 by d...@encosia.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I haven't noticed it being specific to any particular site. In my
experience, any site that uses an <audio> element to embed an mp3 can
exhibit the problem.

[chro...@googlecode.com]

Comment #62 on issue 111281 by Ant...@web.de: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I can try to setup a use case where the issue occurs. Should I provide it
to anybody (I can do this tomorrow evening)?

[chro...@googlecode.com]

Comment #63 on issue 111281 by sche...@chromium.org: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Ant_ha: just update this bug w/ a URL when you get the chance

[chro...@googlecode.com]

Comment #64 on issue 111281 by sche...@chromium.org: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

elmonty: can you clarify "browser locks up"?

For example ... is it just the MP3 player that's locked up? The tab? Or all
of Chrome?

[chro...@googlecode.com]

Comment #65 on issue 111281 by morris.j...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Sorry ... Posted with the wrong account. I will post a URL here. (I was
Ant_ha)

[chro...@googlecode.com]

Comment #66 on issue 111281 by r...@vipasolutions.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

This is easy to reproduce with byte range requests and a clean cache. It
isn't related to max concurrent requests to a domain.

See https://code.google.com/p/chromium/issues/detail?id=111281#c27 for an
explanation.

I don't know about "lock up", but the player stops and the only way to get
it going again is to reload the page.

[chro...@googlecode.com]

Comment #67 on issue 111281 by elmo...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

It varies. Most of the time, the tab just goes into a wait. After 10 to
30 seconds it recovers but any resources - not just MP3 files - that were
queued up to be requested during that time fail to start. Less frequently,
all of Chrome freezes and it won't even close.

[chro...@googlecode.com]

Comment #68 on issue 111281 by jdelStro...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

It occurs semi-frequently with longform audio on Audioboo - eg
https://audioboo.fm/boos/1771116-why-has-president-obama-not-been-able-to-close-guantanamo-bay.
I've only noticed it on longer pieces (say, 20 minutes or more). If you
start playing back the audio, it'll continuing buffering ahead like it's
supposed to for a several minutes, but then seems to give up buffering. At
that point, no amount of scrubbing or stop/starting the audio will fix it,
and you have to reload the page.

I've also seen the problem when using Chrome's 'native' player (eg
https://audioboo.fm/boos/1771116-why-has-president-obama-not-been-able-to-close-guantanamo-bay.mp3).

[chro...@googlecode.com]

Comment #69 on issue 111281 by jdelStro...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

(I should probably point out that I've not tried to reproduce the problem
with that particular MP3 - it's just a long piece of audio that I assume
will reproduce it if I hit it enough times, since it's encoded and hosted
exactly the same as all our other audio. I'll try and verify that the
issue does crop up with it, though it might take me a while)

[chro...@googlecode.com]

Comment #70 on issue 111281 by kie....@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

it happens a lot with audioboo. i can produce it ANY TIME by going here:
http://www.kiddnation.com/category/kpod/

[chro...@googlecode.com]

Comment #72 on issue 111281 by morris.j...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I just want to prepare the demo to reproduce this. I get into this issue
while writing a plugin for ownCloud. Then I want to dig out the music
player from ownCloud and replaced the file deliveries from within ownCloud
(via a PHP script to check for the user etc) to a plain file deliver of the
web server. After this I can't reproduce the issue anymore. I think, it
just occurs when the file get's delivered through PHP and not straight from
the webserver. Hope that this is a relevant. I try to setup a test instance
for you guys.

[chro...@googlecode.com]

Comment #73 on issue 111281 by j.j.mole...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

The link from #70 looks like the same issue as 161713. Server closes
connection after 30s of not being able to send any data to the client and
Chrome doesn't restart the connection.

[chro...@googlecode.com]

Comment #75 on issue 111281 by wolf...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

morris #74,

looking at the dev tools i see an abundance of ownCloudSound: Ignoring
progress
in the console logs. but for me it still plays the music.

It seems to lock up with in the middle of ownCloudSound: progress, 11%
loaded
then you click the next button, as ownCloudSound: suspend is parsed and a
waiting period of multiple ownCloudSound: Ignoring progress is being logged.

That being said there is a delay, but this seems to work under my current
settings.
Win7
GC Version 31.0.1650.57 m

[chro...@googlecode.com]

Comment #76 on issue 111281 by wolf...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

update...there is even a longer delay if you were to click next like 5
times in a row.
it also changes from ownCloudSound to HTML5:: with two colons.

one more thing...GC had to get updated now....
Version 31.0.1650.63 m

ownCloudSound: Using HTML5
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: play(): Attempting to load
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: load
(/owncloud/index.php/apps/files/download/Diablo/02%20-%20Heroines.mp3)
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring timeupdate
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: waiting
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Buffer state change: 1
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: loadstart
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring loadedmetadata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring loadeddata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring canplay
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring canplaythrough
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5::Ignoring stalled
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring suspend
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring stalled
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring stalled
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring stalled
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring stalled
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5::Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring stalled
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5::Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: stalled
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring loadedmetadata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring loadeddata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring canplay
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring canplaythrough
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
HTML5:: Ignoring suspend
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring loadedmetadata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring loadeddata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring canplay
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring canplaythrough
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring suspend
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring loadedmetadata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring loadeddata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring canplay
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring canplaythrough
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring suspend
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring loadedmetadata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring loadeddata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring canplay
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring canplaythrough
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Ignoring progress
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: Buffer state change: 0
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: loadedmetadata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: loadeddata
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: canplay
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: onload()
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1188
ownCloudSound: playing
soundmanager2.js?v=078bdd6990e2259f4c1a7eb5c07a0e69:1190
ownCloudSound: progress, 4% loaded

[chro...@googlecode.com]

Comment #77 on issue 111281 by morris.j...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

@ #75

It occurs sometimes when loading the next song (triggered with "next
button") and then there is this "stalled". After some seconds it loads
properly (from 5 up to 50 seconds)

ArchLinux with Chromium Version 31.0.1650.63 (238485)

[chro...@googlecode.com]

Comment #78 on issue 111281 by norda...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Having the same issue. We're hosting a podcast on Wordpress and they're
usually around 20 minutes long compressed in ogg format (ends up around 15
MB), though we've tried mp3 as well and not surprisingly it has the same
issue.

This happens when played through Wordpress' JS based player and HTML5
through Chrome, even when directly loading the URL to the file in Chrome.
I'm currently using nginx 1.2.1 with PHP 5.4 (although PHP seems irrelevant
at this point since nginx is serving the file). The only things I can think
of that might be causing this are Cloudflare and the PageSpeed addon for
nginx. I've already tried disabling both of those, clearing the cache and,
and trying it again. Still has the same issue.

Additionally gone through many different options/values in the nginx
configuration regarding keepalive, output buffering, gzip compression, and
mime types clearing the cache and checking everytime. The amount of time it
manages to get into the audio file seems to be random. Sometimes it doesn't
even make it to 2 minutes, rarely it will get up to somewhere between 6 and
8 minutes.

As others have noted, this doesn't occur on any other browser. The only
solution I've come across, which may or may not be related, is on this
page: http://stackoverflow.com/questions/10840260/chrome-wont-play-mp3-files

It seems similar but regardless, switching to an outdated version of apache
is currently not an option for us.

Attachments:
1.jpg 130 KB
2.jpg 131 KB
3.jpg 166 KB
4.jpg 152 KB
5.jpg 160 KB
6.jpg 63.9 KB

[chro...@googlecode.com]

Comment #80 on issue 111281 by bcl...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Reproduced in Chrome 32 and other Chromium-based browsers (YaBrowser) on
all versions of Windows (XP, 7, 8, 8.1) when streaming mp3 files from the
web.

Error code is always 2 (MEDIA_ERR_NETWORK).

Probability of the error increases if playback is paused and then continued
after a short interval (2-3 minute or so).

Not all clients are affected. For example from 32 unique visitors, only 9
suffered but at high rate (190 total errors per 9 users).

Probably number of opened tabs or overal network activity matters.

As a workaround I have to handle error event, then seek and continue.

[chro...@googlecode.com]

Comment #85 on issue 111281 by sche...@chromium.org: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

elmonty: note that while I said it was "by design" -- I didn't mention
whether it was good or not :)


(I agree this is causing unnecessary pain for web developers and I'd like
to see it fixed as well)

[chro...@googlecode.com]

Comment #86 on issue 111281 by michael....@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I am having similar issues with video playback. Unable to seek within a
video after 1:28 mins. Under 1:28 mins I am able to seek but not after. -
Chrome v 33

On Firefox it works like a charm. Chrome generates a video error with the
code MEDIA_ERR_NETWORK.

Request headers for that WebM file are:

Request
URL:https://localhost:8080/video/dennis-creighton's-farewell-party/type/mp4?1394167071257
Request Headers CAUTION: Provisional headers are shown.
Accept-Encoding:identity;q=1, *;q=0
Range:bytes=62334667-
Referer:https://localhost:8080/video/dennis-creighton's-farewell-party
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/33.0.1750.146 Safari/537.36
Query String Parametersview sourceview URL encoded
1394167071257:

Really, the request has been cancelled, hence provisional headers are shown.

On the server side, I am using this node library to serve videos the smart
way with ranges:
https://github.com/geta6/connect-stream

Can you please have a look at this and let me know what's the culprit?

Thanks
Michael

[chro...@googlecode.com]

Comment #87 on issue 111281 by markledf...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I have just found another major issue caused by this approach where html5
media is partially loaded and the connection left open until the user plays
or the connection times out. It permanently takes up one of the 6 parallel
connections allowed for each domain, even across tabs. So if you have 6
html5 videos preloaded that are not set to auto play, they will take those
6 slots and all other assets requests to that domain will be queued
indefinitely. Try opening 2 Chrome tabs with the same 6 videos. Note that
the second tab won't load its requests. As soon as you close the 1st tab
you'll see the second start working.

[chro...@googlecode.com]

Comment #88 on issue 111281 by dlcabl...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Streaming podcast stops after 7 minutes. Hewre's an example:
http://conservativestream.com/recorded-shows/Savage_04-02-2014_WCB_FULL.mp3
EVERY time. No problem with any other browser.

Chrome Version 33.0.1750.154

VERY irritating

[chro...@googlecode.com]

Comment #89 on issue 111281 by dlcabl...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Streaming podcast stops after 7 minutes. Here's an example:

[chro...@googlecode.com]

Comment #90 on issue 111281 by dlcabl...@gmail.com: HTML5 audio files stop
buffering
http://code.google.com/p/chromium/issues/detail?id=111281

Same problem with Savage streaming. VERY irritating!

36.0.1985.67 beta-m

[chro...@googlecode.com]

Comment #91 on issue 111281 by cy.unpin...@gmail.com: HTML5 audio files
stop buffering
http://code.google.com/p/chromium/issues/detail?id=111281

I am getting the following error using HTML 5 audio tags on both chrome and
opera: "Failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING"
after the audio plays for between 50 seconds to sometimes one minute and a
half, the audio stops.

This problem does not exist on Firefox.

http://inetwebdesign.com/ClassicalComposers.html

[chro...@googlecode.com]

Comment #92 on issue 111281 by ronleero...@gmail.com: HTML5 audio files
stop buffering
https://code.google.com/p/chromium/issues/detail?id=111281

Chrome is still having this issue.

[chro...@googlecode.com]

Comment #93 on issue 111281 by tanjian...@gmail.com: HTML5 audio files stop
buffering
https://code.google.com/p/chromium/issues/detail?id=111281

I can also confirm that this issue still persist. It also affect video
files such as mp4 as well.

[chro...@googlecode.com]

Comment #94 on issue 111281 by unprofes...@gmail.com: HTML5 audio files
stop buffering
https://code.google.com/p/chromium/issues/detail?id=111281

I confirm. MEDIA_ERR_NETWORK happens in both <audio> and <video>. It
happens only in Chrome, other browsers work fine.

Unfortunately error is not easy to reproduce. It seems it depends on lots
of circumstances.