Open Bug 1923152 Opened 14 days ago Updated 13 days ago

[x11/fvwm] screen sharing crashed on webex.com

Categories

(Core :: WebRTC, defect, P3)

Firefox 131
defect

Tracking

()

UNCONFIRMED

People

(Reporter: vincent-moz, Unassigned, NeedInfo)

Details

Attachments

(1 file)

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

Steps to reproduce:

I did screen sharing (of an Xpdf window) on webex.com.

Actual results:

I got a message saying that something crashed (I don't remember the name and Firefox didn't keep the information) and the other participants were seeing a black screen.

Here's the crash report:
https://crash-stats.mozilla.org/report/index/76a14fa3-7cb5-4dbf-a051-d62110241007

Expected results:

There shouldn't be any crash.

Sharing the concerned window with the same Firefox process works well on the getUserMedia / getDisplayMedia Test Page:
https://mozilla.github.io/webrtc-landing/gum_test.html

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

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

This looks more a WebRTC bug.

Component: Widget: Gtk → WebRTC

The backtrace is incomplete. Can you attach content of about:support page?
Thanks.

Flags: needinfo?(vincent-moz)
Attached file about:support
Flags: needinfo?(vincent-moz)

Do you use plain Mozilla binaries?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries

If not, please try so, run under a new profile and if you see the crash submit it and attach crash ID here. The one you posted is missing all backtrace data.

Thanks.

Flags: needinfo?(vincent-moz)
Priority: -- → P3
Summary: screen sharing crashed on webex.com → [x11/fvwm] screen sharing crashed on webex.com

(In reply to Martin Stránský [:stransky] (ni? me) from comment #5)

Do you use plain Mozilla binaries?

I use Debian's.

If not, please try so, run under a new profile and if you see the crash submit it and attach crash ID here. The one you posted is missing all backtrace data.

First, I'm not sure that a Mozilla binary would help for the backtrace data. In the past, it didn't. See bug 1360392 comment 60 (note: this one was concerning a crash on a different Debian machine and the cause was a buggy driver).

Concerning a new profile, I'm not sure I can: For the connection to the webex.com meeting, I initially tried a new profile a couple of times, but it didn't work at all (the server was saying something like the meeting was no longer active), then when I used the old profile, I could connect to the meeting.

Webex has a meeting test page https://www.webex.com/fr/test-meeting.html and I tried under similar conditions (same profile, sharing an Xpdf window with the same PDF file), but I couldn't reproduce the crash. Note that I haven't rebooted the machine since the crash occurred (yesterday). But things might be different compared to a real meeting with many participants.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: