New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 655342 link

Starred by 4 users

Issue metadata

Status: Duplicate
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Tab Crash: HTML Audio element and setSinkId()

Reported by philipp....@gmail.com, Oct 12 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36

Steps to reproduce the problem:
var mediaElement = new Audio('//s.sococo.com/sounds/02_enter_space.ogg');
mediaElement.setSinkId('default');

What is the expected behavior?

What went wrong?
Chrome Tab crashes

Did this work before? N/A 

Chrome version: 54.0.2840.59  Channel: stable
OS Version: OS X 10.12.0
Flash Version: Shockwave Flash 23.0 r0
 
Windows is also affected.
I experienced the same thing, and I think I have an indication of the problem. I tested with checking that readyState is larger than 1 before I call setSinkId, and then it works. Also if I run setSinkId when the canplay event is fired, it works. 

Maybe the bugfix https://bugs.chromium.org/p/chromium/issues/detail?id=633930# introduced it? At least it states "Make sure WebRtcAudioRenderer always plays sink after starting it."

But I'm not sure what is the correct way to make sure setSinkId can be called without crashing!? Any advice or bugfix is appreciated.

Comment 3 by jmqu...@gmail.com, Oct 13 2016

A workaround that philipp found is to only set the sink id in the 'canplaythrough' event.

mediaElement.addEventListener('canplaythrough', function() {
   mediaElement.setSinkId('default');
   mediaElement.play();
}, false);
Components: -Blink Blink>Media>Audio
Status: Untriaged (was: Unconfirmed)
Cc: mlamouri@chromium.org
Owner: guidou@chromium.org
Status: Assigned (was: Untriaged)
guidou@, can you have a look at this?
Labels: -Type-Bug Type-Bug-Regression

Comment 8 by guidou@chromium.org, Oct 20 2016

Cc: olka@chromium.org
I cannot reproduce this issue. I think it might be a duplicate of issue 627901, which was fixed by olka@. olka@: Do you think this is the case?

phillipp/kristian/jmquigs: Can you still reproduce this problem in Beta/Canary?

Comment 9 by olka@chromium.org, Oct 20 2016

Could you check if it's reproducible at 54.0.2840.61+?

It would help to see a crash or a backtrace of it.

Comment 10 by mfar...@gmail.com, Oct 21 2016

I reported:

https://bugs.chromium.org/p/chromium/issues/detail?id=657600

Which appears to be a duplicate of this bug.  I tested a few minutes ago with 54.0.2840.71 and it appears that the crashes are no longer happening (even with the jsbin code that I posted in 657600).  This definitely happened in54.0.2840.59 but I can't get it to happen anymore with .71.

I have some notes in the other case - but we did not see this issue on Chrome 53, or Chrome 55 (beta) or Chrome Canary when I reported it.... just Chrome 54.

From my standpoint - this is now working great!
Just got around to test this, and can confirm that it does not crash in 54.0.2840.71.
Mergedinto: 627901
Status: Duplicate (was: Assigned)

Sign in to add a comment