SendCreateAudioIPCConnection failed: invalid FD
Categories
(Core :: Audio/Video: cubeb, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox96 | --- | unaffected |
firefox97 | --- | unaffected |
firefox98 | blocking | disabled |
firefox99 | --- | fixed |
People
(Reporter: lukas.bernhard, Assigned: kinetik)
References
(Regression)
Details
(Keywords: nightly-community, regression)
Attachments
(1 file)
(deleted),
text/x-log
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0
Steps to reproduce:
Using Firefox Nightly (ASAN build) on ubuntu 21.10.
Actual results:
Audio stops working after using the browser a couple of minutes; however it does work initially. Also, firefox asks whether I'd like to install PulseAudio (which is installed already).
I ran Firefox with 'MOZ_LOG=MediaDecoder:5,AudioStream:5,cubeb:5' and am attaching the logs.
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Thanks for reporting this! I'll investigate. As a workaround, you can flip the pref "media.cubeb.sandbox_v2" to false and restart Firefox to avoid this issue.
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Set release status flags based on info from the regressing bug 1726279
Comment 3•3 years ago
|
||
We have multiple reports of audio being broken on Linux since the landing of bug 1726279. Setting as blocker for 98 as we can't ship without audio on a tier 1 platform.
Comment 4•3 years ago
|
||
Changing the priority to p2 as the bug is tracked by a release manager for the current nightly.
See What Do You Triage for more information
Assignee | ||
Comment 5•3 years ago
|
||
Bug 1750810 will revert this change for Linux in Nightly 98 until the existing issues are resolved.
Assignee | ||
Comment 6•3 years ago
|
||
This is still disabled via bug 1750810, so not currently affecting 98.
Assignee | ||
Comment 7•3 years ago
|
||
This is likely fixed by the same change required to solve bug 1750477.
Assignee | ||
Comment 8•3 years ago
|
||
The fixes in bug 1757473 should address this issue.
Assignee | ||
Comment 9•3 years ago
|
||
Fixed by bug 1757473.
Updated•3 years ago
|
Description
•