Muted tab still plays audio
Reported by
hakerh403@gmail.com,
Oct 6 2017
|
||||||
Issue descriptionUserAgent: ’\_(ツ)_/‘ Example URL: All urls Steps to reproduce the problem: 1. Mute the tab 2. Open a webpage (in that tab) which plays sound (for example a youtube video) 3. Press CTRL+W (to close the tab) 4. Notice that sound is played for about ~100 milliseconds What is the expected behavior? No sound should be played at all. What went wrong? I don't know why, but sound is played for a very short time before the tab is closed. But, a muted tab should not play sound at all. Probably Chrome is unmuting tab before closing it, I don't have other explanation. Did this work before? No Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: 6.3 Flash Version: Flash? What is it? Is it some cake? Contents of chrome://gpu: "Please open a new tab on URL chrome://gpu and paste that text here." ---> No need for it, because the problem is not related just to my system, it is related to Chrome. I tested it on Windows and on Linux and on different architectures and the issue is still present. Any other comments? No.
,
Oct 6 2017
I'll take this one. It'll likely be resolved with my upcoming work on the audio service. Root cause sounds like a race between AudioMirroringManager and the audio output stream being shut down from the renderer. AudioMirroringManager may be getting the tab close notification 100 ms before audio output stream is closed over in AudioRendererHost.
,
Oct 6 2017
Issue 574265 has been merged into this issue.
,
Oct 13 2017
,
Mar 6 2018
,
Mar 6 2018
I'm working on rewriting some of the loopback and muting infrastructure to support the new AudioService effort. Should be obvious to improve the design to prevent this from happening. (So, I'm not trying to fix the bug, but replace the impl with one that works.)
,
Mar 6 2018
Issue 810010 has been merged into this issue.
,
May 19 2018
,
Dec 18
No more action to take on this bug. It will be completely fixed when the Audio Service is fully rolled-out (which is already the case on some platforms). |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dalecur...@chromium.org
, Oct 6 2017