Audio instantiation times out after 30 seconds in Chrome 52
Reported by
julie.si...@gmail.com,
Aug 8 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Example URL: https://jsfiddle.net/6pa4xkbp/ Steps to reproduce the problem: 1. Click 'run' on the JSFiddle 2. Wait for the 31 second timeout as indicated by the alert that pops up 3. Note that no audio plays What is the expected behavior? Audio should play. If you reduce the timeout to less than 30 seconds or try in Chrome 51 or other browsers, the audio does play What went wrong? We have a button that will read audio to students and sometimes they wait more than 30 seconds to click play. That works fine in all browsers (including Chrome 51), but we have had several support issues due to the fact it no longer works in Chrome 52. Did this work before? Yes Chrome 51 Is it a problem with Flash or HTML5? N/A Does this work in other browsers? Yes Chrome version: 52.0.2743.116 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 22.0 r0 Several others have noticed this bug here: https://github.com/goldfire/howler.js/issues/593
,
Aug 9 2016
,
Aug 9 2016
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.6 using chrome version 52.0.2743.116 .This working fine on beta 53.0.2785.46 and canary version 54.0.2824.0.Please find the reverse bisect information as below Narrow Bisect:: Good :: 53.0.2744.0 - ( official build revision 395221) Bad:: 52.0.2743.116 - ( official build revision 394939) Providing manual change log as the good and bad builds are from 2 different milestones. Change Log:: https://chromium.googlesource.com/chromium/src/+log/52.0.2743.0..53.0.2744.0?pretty=fuller&n=10000 Unable to find the exact suspect from the above change log.Could any one from dev team please look into this issue. Thanks,
,
Aug 9 2016
Hmm, on another bug someone reported this was an issue with Howl, but I can't find that other bug right now.
,
Aug 9 2016
someone mentioned on the github issue list that he thought it was Howl, but then later he realized he was wrong. Given this works in Chrome 51, Chrome 53 and all other browsers, I do not think this is a Howl issue. from https://github.com/goldfire/howler.js/issues/593: @nmrugg I had filed an issue with Chromium when I thought the problem was with the web audio API. Since it turned out to not be that API, that bug is closed. I didn't open a different one for the suspend/resume not working as expected since I hadn't gotten familiar with that code or narrowed down which part is the problem with Chrome 52.
,
Aug 9 2016
+WebAudio folk.
,
Aug 11 2016
It would be really nice to have a repro case that didn't involve Howl, which comment #5 is not actually involved. Also, the change log from comment 3 shows only 2 changes to webaudio, neither of which are obvious candidates for fixing the issue.
,
Aug 12 2016
as per #1, this issue not repro on 53.0.2785.46 beta. Do we still need port the fix?
,
Aug 15 2016
Probably we would not get approval to merge any fix to M52 for this, though it would be good to know what was fixed.
,
Aug 15 2016
Anybody oppose to my closing this bug as won't fix then?
,
Aug 16 2016
This is ok. I was hoping it was an obvious change. I'm glad it's working in v. 53!
,
Aug 17 2016
,
Aug 24 2016
Adding an update to this bug in case anyone looks back on it. I think what is happening here is that Chrome 52 must not register activity on the page the same way other browsers / Chrome 51 and Chrome 53 do because Howler is registering 30 seconds of inactivity on the page and timing out on Chrome 52 only.
,
Aug 24 2016
+avayvod@ who was looking at something similar. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by julie.si...@gmail.com
, Aug 8 2016