Issue metadata
Sign in to add a comment
|
Max hardware contexts error on page with AudioContext opened from link with target="_blank" |
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Example URL: http://output.jsbin.com/kodoxuhuqu Steps to reproduce the problem: Example source: http://jsbin.com/kodoxuhuqu/edit?html 1. Load example page (http://output.jsbin.com/kodoxuhuqu) 2. Ctrl-click the first link 6 times to get 7 total tabs with AudioContexts. The 7th tab will display an error. 3. Repeat for the second and third links; the 7th (8th, etc) tab for each will successfully create an AudioContext. What is the expected behavior? AudioContext should behave the same regardless of the value of target. What went wrong? The full error from the target="_blank" example is: NotSupportedError: Failed to construct 'AudioContext': The number of hardware contexts provided (6) is greater than or equal to the maximum bound (6). Did this work before? N/A Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 49.0.2623.87 Channel: stable OS Version: 14.04 Flash Version: Shockwave Flash 21.0 r0 The same issue does not appear in Firefox 44.0.2.
,
Mar 18 2016
Sorry about that, didn't realize jsbin has an expiration for pasted code. Here's the example: http://cmschudel.github.io/chrome-audioctx-example.html
,
Mar 18 2016
Thank you for providing more feedback. Assigning to requester "yiningc@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 1 2016
Any update on this issue? Thanks.
,
Jun 3 2016
,
Jul 27 2016
cschudel@google.com, I am able to repro this bug. But in my repro, I see the same behavior on 2nd(nonempty target) and 3rd(no target) link in your repro page. I think this is more like a blink bug since it involes AudioContext API. Blink folks, if you think this is a media bug, please assign back.
,
Aug 9 2016
,
Nov 28 2016
Tabs which share render process also share this AudioContext instance count limit. It would be nice if the limit didn't exist (why is it there?) or if the limit applied to a tab's JS context instead of the process.
,
Dec 7 2016
,
Dec 8 2016
Yes, there is a limit of 6 audio contexts (but used to be 4). I do not know why; there's always been a limit, but there's no documentation of why.
,
Dec 8 2016
Probably a speculative concern on the number of threads. Each AudioContext creates a new thread and this certainly impacts the performance of the browser. With that said, we need to revisit this issue.
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
Oct 11 2017
cschudel@ Currently we don't have a plan to support more than 6 concurrent AudioContexts. Do you have a use case for it?
,
Oct 13 2017
Multiple pages (even from different sites) in the same render process can reach the AudioContexts limit quickly. I think user behavior around "Open link in new tab" is the primary cause; just a few extra tabs open on a site which uses WebAudio can cause this problem.
,
Oct 13 2017
Right, as andrew.vermie@ says, we run into this limit frequently because our users tend to "Open link in new tab", and the opened pages all load audio.
,
Feb 1 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by yini...@chromium.org
, Mar 17 2016