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

Issue 629440 link

Starred by 3 users
Status: Duplicate
Merged: issue 644622
Owner: ----
Closed: Sep 2016
Cc:
guidou@chromium.org
dalecur...@chromium.org
█ olka@chromium.org
solenberg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Abort Error setSinkId with default audio output after removing used output device

Reported by jauhenka...@gmail.com, Jul 19 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Set some sound output USB device as default in your OS
2. setSinkId to the device
3. Remove USB device (Default sound output device is Laptop speakers in OS in my case)
4. setSinkId to the default

What is the expected behavior?
Sound output device should be default one.

What went wrong?
Get Abort Error.

Did this work before? No 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? N/A 

Chrome version: 51.0.2704.103  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0

Comment 1 by yini...@chromium.org, Jul 21 2016

Components: -Internals>Media Internals>Media>Audio
jauhenkarmyzau@gmail.com, is this a regression from prior chrome build?

Comment 2 by yini...@chromium.org, Aug 15 2016 

ping jauhenkarmyzau@gmail.com again. Is this a regression from prior build?

Comment 3 by jauhenka...@gmail.com, Aug 31 2016 

It was a regular chrome version, not beta or something.

Comment 4 by yini...@chromium.org, Sep 6 2016 

did this issue happen on prior chrome build?

Comment 5 by yini...@chromium.org, Sep 6 2016

Cc: dalecur...@chromium.org
dale, have you heard any similar issue before? any idea what's the possible reason?

Comment 6 by dalecur...@chromium.org, Sep 6 2016

Cc: guidou@chromium.org

Comment 7 by jauhenka...@gmail.com, Sep 7 2016 

Yes, it was a prior chrome build. See the issue description.

Comment 8 by guidou@chromium.org, Sep 8 2016

Cc: olka@chromium.org

Comment 9 by guidou@chromium.org, Sep 21 2016

Mergedinto: 644622
Status: Duplicate (was: Unconfirmed)
This is almost certainly a duplicate of  crbug.com/644622
►

Sign in to add a comment