New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 692661 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

<audio> retries too many times on network failure

Project Member Reported by johnplaisted@google.com, Feb 15 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Create an <audio> note and set the src to a large, valid file.
2. Invalidate the file server-side so that any further requests for it return an HTTP error (ie 403).
3. Do something that will cause the audio node to make a new request for its source, like seeking outside of the buffered range.

What is the expected behavior?
The audio node should throw an error event much sooner on HTTP 400/500.

What went wrong?
The audio node retries the request, which now 400s every time, many times (I've seen it retry 31 times) before throwing an error event.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 
Flash Version: 

Seems to be N/A on FireFox, or at least harder to reproduce since it downloads the entire file as fast as possible. Chrome only downloads a few MB at a time so its easy to trigger by seeking.

 
Cc: wolenetz@chromium.org
Components: -Blink>Media Internals>Media>Network
Owner: hubbe@chromium.org
Status: Assigned (was: Unconfirmed)
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 27 2017

Labels: Hotlist-Google

Comment 3 by hubbe@chromium.org, Oct 5 2017

I'm not sure if this ia bug we really want to fix.
It's possible that the error is transient and will recover shortly.

Comment 4 by hubbe@chromium.org, Mar 8 2018

Status: WontFix (was: Assigned)

Sign in to add a comment