1876896 - crash when accessing Pipewire camera from multiple tabs

Status: VERIFIED FIXED

(Core :: WebRTC, defect)

Description

[Be]

Attachment: firefox-backtrace.txt

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0

Steps to reproduce:

1. Set media.webrtc.camera.allow-pipewire to true in about:config
2. Go to https://webrtc.github.io/test-pages/src/single-video/ and give it access to a camera via Pipewire
3. Open another tab of https://webrtc.github.io/test-pages/src/single-video/ or any other page accessing a camera via WebRTC

Actual results:

Firefox crashes (see attached backtrace)

Expected results:

Camera feed is available to all tabs simultaneously via Pipewire

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Andreas Pehrson [:pehrsons]]

This is upstream bug 15211. Jan, do you have anything on file in bugzilla already?

Comment 3

[Jan Grulich]

(In reply to Andreas Pehrson [:pehrsons] from comment #2)

This is upstream bug 15211. Jan, do you have anything on file in bugzilla already?

I don't. I will backport the upstream fix now.

Comment 4

[Jan Grulich]

Attachment: Bug 1876896 - WebRTC backport: Allow VideoCaptureModulePipeWire to be shared with more consumers r=pehrsons

This is a simple backport of an WebRTC upstream change.

Upstream commit: 958c9ac546f33716d097b5092515dcac705151d3

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/2ba2ef65280b
WebRTC backport: Allow VideoCaptureModulePipeWire to be shared with more consumers r=pehrsons,webrtc-reviewers

Comment 6

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/2ba2ef65280b

Comment 7

[Be]

Thanks for fixing this!

Comment 8

[Ina Popescu, Desktop QA]

I've successfully replicated this issue using Nightly 124.0a1(2024-01-26) on Ubuntu 22.04 following the STR from Comment 0.
Verified as fixed in the latest Firefox 124 version, within the same configuration, where the issue no longer persists.