Failure loading 130 <audio> tags
Fixed Issue #8238360
Details
- Author
- cats n.
- Created
- Jul 21, 2016
- Privacy
- This issue is public.
- Found in
- Found in build #
- 16.16299
- Fixed in build #
- 17.17692
- Reports
- Reported by 1 person
Sign in to watch or report this issue.
Steps to reproduce
When there are 130 pieces to describe the <audio> on 1 page , some of the mp3 files will fail to load.
UPDATE
NOTE: nginx is not required in order to repro, however, the content must be served from a web server not from local files
It will occur in the nginx-1.9.9 (but we may need to test a more recent version) on the windows 10. It does not occur locally.
It does not occur in the first time of the load.
It occurs when you reload.
Steps to Reproduce.
- Cache Delete
- Load the audio.html (included in the attached ZIP)
- reload the audio.html (“Invalid resource” will occur at random)
Still seeing this issue in Microsoft Edge 16299
Comments and activity
-
Microsoft Edge Team Changed Assigned To to “Travis L.”
Changed Assigned To to “Venkat K.”
Changed Assigned To from “Venkat K.” to “Jerry S.”
-
It will occur in the nginx-1.9.9 on the windows 10.
It does not occur locally.It does not occur in the first time of the load.
It occurs when you reload.It is Steps to Reproduce.
- Cache Delete
- Load the audio.html (It will succeed)
- reload the audio.html (“Invalid resource” will occur at random)
Why do you fail (“Invalid resource”) to reload?
Use browser:
Microsoft Edge 25.10586.0.0 Microsoft EdgeHTML 13.10586
and
Internet Explorer 11 (11.494.10586.0) -
Changed Status to “Needs root cause”
- Microsoft Edge Team
Changed Assigned To from “Jerry S.” to “Angelo L.”
Changed Assigned To from “Angelo L.” to “Gurpreet V.”
Changed Status from “Needs root cause” to “Not reproducible”
-
Hello,
Thank you for providing this information about the issue. We are no longer able to reproduce this problem in Edge. Please test this behavior in our latest public stable build 16299.
Best Wishes,
The MS Edge Team -
Hello!
thank you for your answer.
I tried it with build 16299.
Unfortunately the situation did not change.
The part of “Invalid resource” changes every time I reload.
What is the cause of “Invalid resource” ?Version:
Microsoft Edge 41.16299.371.0
Microsoft EdgeHTML 16.16299 - Microsoft Edge Team
Changed Steps to Reproduce
Changed Status from “Not reproducible” to “Needs root cause”
Changed Status from “Needs root cause” to “Not reproducible”
Changed Steps to Reproduce
Changed Assigned To to “Gurpreet V.”
Changed Status from “Not reproducible” to “Needs root cause”
Changed Assigned To from “Gurpreet V.” to “Matthew H.”
Changed Steps to Reproduce
Changed Title from “Failure to read the <audio>” to “Failure loading 130 <audio> tags”
Changed Assigned To from “Matthew H.” to “Glenn E.”
Changed Status from “Needs root cause” to “Confirmed”
Changed Status from “Confirmed” to “Fixed”
-
Hello,
Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge and will be available in an upcoming insider build.
Best Wishes,
The MS Edge Team
You need to sign in to your Microsoft account to add a comment.
Sign in