Open Bug 1458034 Opened 2 years ago Updated 9 months ago
Multiple sound output on Windows 10 1803
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180426170554 Steps to reproduce: Install the latest public release of Windows, the version 1803 and any up to date release of Firefox (60.0b16 here). Open the sound preference of Windows and go to "App volume and device preferences". Actual results: Multiple sound outputs are listed. The number is not related to the number of tabs. Expected results: Only one sound output should be listed.
Can confirm. Same build of FF I'm on the slow lane of the windows insider preview program. Windows 10 Pro Version: 1803 OS Build: 17134.1 You can see the effects of this problem by right cliking volume icon in the taskbar and selecting open volume mixer.
Component: Untriaged → DOM: Content Processes
OS: Unspecified → Windows 10
Product: Firefox → Core
The same for Win 10 Pro Version 1709 and latest Firefox Nightly (61). Actually latest Nightly is even worse than latest release (59.0.3): with Nightly there are about 20 sliders while only 8 tabs opened, while with latest - about 10 sliders for the same 8 tabs.
Also it looks like Windows Server 2016 Version 1607 is not affected: with many tabs (40+) opened there is just one slider for the Firefox (latest - 59.0.3, not nightly).
Windows 10 Pro - 1803 I see this as well in Nightly and 60.0.1. It seems like Windows creates a volume slider for nearly every running process. But only in the new sound mixer. The old mixer doesn't have this amount of selection for me. By comparison: Microsoft Edge will create a mixer for every tab that has media in it. Google Chrome will create a mixer for every tab that has media in it and give it the title of the source tab. Chromium Based browsers all follow Chrome's lead.
Same problem. Is there a workaround other than deactivating multiple processes for Firefox (= setting browser.tabs.remote.autostart to False in about:config)?
There will be also multiple entries for Firefox in Windows 1803/1809 --> Preferences --> System --> Sound --> extended options. But only one slider is active, the others are without any sound-function.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 20181020102231 :jimm, 6 months have gone by since I set a NeedInfo flag for the assignee of bug 1358372, but he hasn't had a look at this. Any ideas to move this forward? In bug 1358372, comment 48, you said you still get multiple volume sliders, but don't know how to reproduce the issue. Does the STR below help? STR: In the Settings window, multiple entries are listed right off the bat: 1. Open Windows Settings → System → Sound → App volume and device preferences. For the old volume mixer, 1. Open the Windows volume mixer from the taskbar icon. 2. In Firefox, open a YouTube channel's video listing page, e.g. https://www.youtube.com/user/BadLipReading/videos 3. Ctrl+click a video to open it in a new tab, e.g. https://www.youtube.com/watch?v=RKOZgQy8qrw 4. Switch to that tab. If the doorhanger prompt pops up, keep the "Remember…" option checked, then click "Allow". 5. Close that tab. 6. Ctrl+click another video to open it in a new tab, e.g. https://www.youtube.com/watch?v=gCMw3AhWBkA 7. Switch to that tab. Actual results: There are 2 "Firefox Nightly" entries in the volume mixer. Expected results: 1 "Firefox Nightly" entry in the volume mixer and "App volume and device preferences".
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
See Also: → 1358372
As note... the issue I'm reporting in 1500683 is that while the MIXER is LEFT OPEN, sliders are not being destroyed. If the volume mixer is closed and reopened the number of sliders is correct (at least as far as my observations went).
I'll find someone to take a look, thanks.
(In reply to Yani from comment #9) > As note... the issue I'm reporting in 1500683 is that while the MIXER is > LEFT OPEN, sliders are not being destroyed. If the volume mixer is closed > and reopened the number of sliders is correct (at least as far as my > observations went). I can confirm this, exactly as you said.
You need to log in before you can comment on or make changes to this bug.