User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Build ID: 20160922183953 Steps to reproduce: A page embeds fifteen WEBM videos that are all hosted on the same server. I (re)load the page. Actual results: Occasionally one or more video previews do not show up, and/or one or more videos do not play. Instead these video areas display an error. Depending on the Firefox version used, the error message is: "Video playback aborted due to a network error." "Video format or MIME type is not supported." I can replicate this with versions 49.0, 51.0b12 and 53.0a1. Firefox' network monitor shows ~0ms 0 bytes when videos fail to load. The occasional errors only show up in Linux (Mint). It does not matter if safe mode is enabled or not. Chromium on Linux does not have the occasional errors. Firefox (50.1.0) in Windows (Wine, to be exact; Windows emulator) does not have the occasional errors. Adding "AddType video/webm .webm" to .htaccess does not fix the occasional errors. I know a workaround. Changing network.http.max-connections from 900 to 1 fixes the problem. Speculation: - Maybe the server limits simultaneous connections per host, and Firefox for Linux doesn't deal with this properly. Firefox for Windows, and Chromium for Linux do not have the problem. - Maybe it matters that the videos are large (20MB+). Expected results: All videos previews should show up, and all videos should play.
Can you provide a link that reproduces the issue?
(In reply to Anthony Jones (:kentuckyfriedtakahe, :k17e) from comment #1) > Can you provide a link that reproduces the issue? Yes, visit with Firefox on Linux: http://forum.princed.org/viewtopic.php?f=118&t=3323 You may immediately see that some don't load properly. Even if they all do, click play on those that seem to be ready. If all work, reload the page to retry. Just now I could immediately reproduce the issue here. "Video playback aborted due to a network error."
Setting network.http.max-persistent-connections-per-server=12 fixes the issue.
Priority: -- → P1
I can also reproduce this in Firefox 53 on Window 10 and OSX 10.12.
Change network.http.max-persistent-connections-per-server does not work for me.
Assignee: nobody → kaku
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.