Closed Bug 1900495 Opened 2 years ago Closed 1 year ago

Firefox 126 crash in [@ @0x0 | st_pbo_draw ] in Mesa 24.1.0 with Intel + Nvidia dualGPU

Categories

(Core :: Widget: Gtk, defect)

Firefox 126
x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: heitorrdpp, Unassigned)

References

Details

(Keywords: crash)

Crash Data

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

Steps to reproduce:

Firefox started randomly crashing after 126 update. It may be just an impression but I think using YouTube the crashes are more frequent.

Actual results:

Firefox would simply crash and close the browser.

Expected results:

Firefox should not crash for no reason.

I am on a fresh install of EndeavourOS and only using UBlockOrigin extension.
Crash report: https://crash-stats.mozilla.org/report/index/6ef63319-ece4-419c-bd86-490850240603

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

Thanks for the report!
Please check if starting Firefox with MOZ_ENABLE_WAYLAND=0 environment variable (or never switching to the Nvidia GPU) avoids the crash. Then it would likely be bug 1898476.
$ MOZ_ENABLE_WAYLAND=0 path/to/firefox

Crash Signature: [@ @0x0 | st_pbo_draw ]
Keywords: crash
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Summary: Crashes in Firefox 126 → Firefox 126 crash in [@ @0x0 | st_pbo_draw ] in Mesa 24.1.0 with Intel + Nvidia dualGPU

The bug has a crash signature, thus the bug will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

(In reply to Darkspirit from comment #3)

Thanks for the report!
Please check if starting Firefox with MOZ_ENABLE_WAYLAND=0 environment variable (or never switching to the Nvidia GPU) avoids the crash. Then it would likely be bug 1898476.
$ MOZ_ENABLE_WAYLAND=0 path/to/firefox

Thank you for the reply! So I tested it for a couple of minutes with the variable set, didn't have any crashes yet, but I am not sure if it is a firefox related issue anymore, since KWin also started crashing. And from what I could tell both crashes are on the Intel GPU actually. I am trying to troubleshoot at the moment, but I don't have much experience with this type of thing.

The bug still happens on Nobara Linux 39
Running with MOZ_ENABLE_WAYLAND=0 the performance on videos is terrible, completely unusable.
When I ran it with MOZ_ENABLE_WAYLAND=0 it outputed:

[Parent 11289, Main Thread] WARNING: Theme directory actions/32 of theme Papirus-Colors-Dark has no size field
: 'glib warning', file /builddir/build/BUILD/firefox-126.0/toolkit/xre/nsSigHandlers.cpp:187

(firefox:11289): Gtk-WARNING **: 19:41:58.876: Theme directory actions/32 of theme Papirus-Colors-Dark has no size field

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.37354) [GFX1-]: glxtest: ManageChildProcess failed

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.37354) |[1][GFX1-]: No GPUs detected via PCI
 (t=0.37354) [GFX1-]: No GPUs detected via PCI

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.37354) |[1][GFX1-]: No GPUs detected via PCI
 (t=0.37354) |[2][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=104.012) [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt

The glxtest message wasn't present before.
Also the KWin crashes stopped happening on Nobara, which makes me believe I was having two different problems simultaneously on Endeavour.
Talking to people online, they also seem to be having problems with firefox 126 on videos supposedly, so maybe this is actually an issue with firefox?

It may be related to Bug 1902589 - Multi GPU crashes on Mesa 24.0.7+

See Also: → 1902589

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.