New issue
Advanced search Search tips

Issue 634444 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Web audio API won't play audio after Chrome has been idle for 30 seconds

Reported by mnewc...@cainc.com, Aug 4 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:47.0) Gecko/20100101 Firefox/47.0

Example URL:

Steps to reproduce the problem:
1. Unzip attached small test case
2. cd to its directory
3. npm install
4. npm start (note: this opens a browser window pointed at the test page)
5. listen to the audio play
6. Wait 30 seconds to the clip to replay (this clip won't be heard but it goes through the various playing states correctly)
7. Switch to the HTML5 audio test case by clicking the link at the bottom of the page, then repeat steps 5 and 6, where for step 6 the audio will be heard in this case.

What is the expected behavior?
The audio should be able to be heard when the clip is replayed after the browser tab has been idle for 30 seconds

What went wrong?
The repeated plays of the audio file are not audible after the tab has been idle for 30 seconds

Did this work before? Yes Chrome 51

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes 

Chrome version: 52.0.2743.82 (64-bit)  Channel: stable
OS Version: OS X 10.11
Flash Version: Shockwave Flash 21.0 r0
 
chrome_audio_bug_test.zip
31.1 KB Download

Comment 1 by mnewc...@cainc.com, Aug 5 2016

From trying a test case of using the web audio api directly (attached), it looks like this is not a bug with the web audio api.  From investigating a bit more, it looks to be that howler has an auto-suspend/resume feature that kicks in after 30 seconds of inactivity and from trying the original test case and manually disabling suspending, that seems to be the culprit.  I'll open an issue with howler's bug tracking so they can investigate what in Chrome 52 caused this to break since I didn't see this problem in Chrome 51.
chrome_audio_bug_test_no_howler.zip
31.4 KB Download
Status: WontFix (was: Unconfirmed)
It sounds like this is not a Chrome bug, then, so I'll mark this WontFix. Please reopen it if I've misunderstood.

Comment 3 by mnewc...@cainc.com, Aug 5 2016

I'm fine with closing this bug, but I just wanted to add a link to the Howler issue in case anyone else comes across this issue: https://github.com/goldfire/howler.js/issues/593

Sign in to add a comment