Firefox crashing (132.0)

putt1ck

Since updating on the 29th of October to Firefox 132 I have experienced consistent crashes - consistent in that certain pages/sites will lead to a fail.

Tried re-downloading and reinstalling FF via Octopi. Tried starting with a clean profile and visiting one of these known URLs still causes the crash.

Installed version reports Mozilla Firefox 132.0 20241028133945 20241028133945

Downloading Firefox from Mozilla (also 132.0) and the same known URLs do not cause a crash (the Mozilla binary is being launched using the same profile).

Running Firefox from CLI gets this error captured on crash
Exiting due to channel error. Exiting due to channel error. Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=28.9198) Segmentation fault (core dumped)
(the "exiting due to channel error is repeated a few times, but seems to occur before crashes are triggered).

nezzie

#putt1ck.
In our imagination perhaps.!!! Either there are not many folk using FF or we are the exceptions with problems.
I have the same problems. Have tried new installs, live usb's, deleting .mozilla and all cache files. Removal of Firefox and reboot and reinstall, creating new profiles etc, different PC's. All give same results as yours.
An adapted Firefox build from elsewhere runs just fine with old profiles and creating new ones.
Been running the adapted FF for about a month now with no problems, all websites load OK.
Perhaps it's our graphics that causes it but 3 PC with different graphics ought to rule that out.

demm

Can either of you open a bug report? Forum is not the best place to debug an app.
Try to add as many logs as possible, in the meantime, I'll check if I can find if some build changes were needed for 132, or if this is rust related.
https://github.com/KaOSx/apps/issues

And to rule out some of the obvious, is the used mirror synced? System full up to date (meaning, no ignore packages, or self-build not up to date or missed needed rebuild)? What version of nss?

nezzie

#Demm
In my case all is updated, mirrors are correct and synced. Also on a clean install. It's happened with FF132 & 131.
Also on an OS with testing enabled. Will give it some more time tomorrow on a clean install. (Again).

demm

Installing is not a fix, please open a bug report with your system as is, and give as much info as possible. Just the info that 131 was also effected already helps. Then this could be related to the new Toolchain/GCC 14. But without detailed logs, it is still just guessing.

Please don't continue here, issues is the place to gather all the needed info.