Closed Bug 1750444 Opened 3 years ago Closed 3 years ago

SendCreateAudioIPCConnection failed: invalid FD

Categories

(Core :: Audio/Video: cubeb, defect, P2)

All
Linux
defect

Tracking

()

RESOLVED FIXED
99 Branch
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)

Attached file audioipc2_server.log (deleted) —

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.

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.

Severity: -- → S3
Flags: needinfo?(kinetik)
OS: Unspecified → Linux
Priority: -- → P3
Regressed by: 1726279
Hardware: Unspecified → All
Has Regression Range: --- → yes
Flags: needinfo?(kinetik)
Keywords: regression
Flags: needinfo?(kinetik)

Set release status flags based on info from the regressing bug 1726279

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.

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

Priority: P3 → P2

Bug 1750810 will revert this change for Linux in Nightly 98 until the existing issues are resolved.

Assignee: nobody → kinetik
Status: NEW → ASSIGNED
Flags: needinfo?(kinetik)

This is still disabled via bug 1750810, so not currently affecting 98.

This is likely fixed by the same change required to solve bug 1750477.

The fixes in bug 1757473 should address this issue.

Depends on: 1757473

Fixed by bug 1757473.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: