WebAudio API don't throw exception for big chain of nodes
Reported by
sss1...@gmail.com,
Apr 4 2016
|
|||||
Issue descriptionChrome Version : any OS Version: any URLs (if applicable) : none Other browsers tested: unknown What steps will reproduce the problem? 1. edit attached file and change var chainSize=400; to bigger value 2. open the file in Chrome browser 3. listen and repeat step 1 What is the expected result? browser play noise or console show error What happens instead of that? for big number some weak PCs and phones stops play noise without any error Please provide any additional information below. Attach a screenshot if possible. this is inappropriate behaviour. I need a way to know if there aren't enough power to switch off some filters programmatically i think it should throw exception UserAgentString: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36
,
Apr 4 2016
Audio is choppy when playing on an ancient Galaxy Nexus. Doesn't actually stop playing, though. @sss1024: Please tell us what devices you used where the audio stops playing.
,
Apr 4 2016
Oh, and there's never been a requirement for WebAudio to throw an exception in this case.
,
Apr 4 2016
keep in mind, there's never been a requirement for WebAudio to stop sound in this case. I found this wrong behaviour on desktop Dell Inspiron 530, phone Lenovo S850, table Samsung Galaxy Tab-E. A modern PC works fine.
,
Apr 4 2016
True, but see also http://webaudio.github.io/web-audio-api/#audio-glitching This will take some work; the devices you say the audio stops on all appear to be at least as powerful if not more powerful than the Galaxy Nexus I tested with.
,
Apr 4 2016
No relation of this bug with your link. Moreover, i attached AnalyserNode to end of chain and dump array from AnalyserNode.getFloatFrequencyData() to console. For tested devices I see right array output but there no sound.
,
Apr 4 2016
Interesting. So it's not a CPU loading issue. You get the expected data, but there's actually no output at all? What about if you reduce the chain size? I assume there is audio output once the chain size gets small enough. I think, then, that there's no way for me to debug this unless I can reproduce this with one of the devices you've mentioned or find some other device that has the same issue.
,
Apr 4 2016
increase value of chainSize variable to reproduce problem on your Galaxy Nexus. About 200 users of my app report this problem.
,
May 26 2016
See https://github.com/WebAudio/web-audio-api/issues/577 Under-run detection moved to v.next in the spec.
,
May 29 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 21 2017
Closing as WontFix. When the issue in c#10 is resolved, we'll reopen or file a new issue about this. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rtoy@chromium.org
, Apr 4 2016