Firefox crashing a lot

[pilotgi]

@Tuner

I also had this problem in Firefox 127 until I disabled hardware acceleration:

Settings → Performance → Uncheck “Use recommended performance settings,” then uncheck “Use hardware acceleration when available”

I don’t think Firefox has crashed since then.

I’m going to try this.

[C7NhtpnK]

@pilotgi

I started Firefox from a new profile and when it crashed I got this:

kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: “Mozilla Firefox” msgid_plural: “” msgc txt: “”
[GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1#67: error 5: explicit sync is used, but no release point is set

and

@pilotgi

@Tuner

I also had this problem in Firefox 127 until I disabled hardware acceleration:

Settings → Performance → Uncheck “Use recommended performance settings,” then uncheck “Use hardware acceleration when available”

I don’t think Firefox has crashed since then.

I’m going to try this.

Well, I am not an export, but what I know:

• Firefox does heavily interact with Graphics… (more than many other applications)
• → try not the latest bleeding edge Nvidia drivers, but standard ones (standard or legacy or system provided) (at least for troubleshooting)
• → try not Wayland, but X instead (at least for troubleshooting)
• → try not KDE or Gnome, but something simpler instead (like Xfce) (at least for troubleshooting)
• like already mentioned, try without internal hardware acceleration — yes, this is probably not satisfying for future use, but good for troubleshooting
• I know that there is a specific KDE patch when using Firefox from openSUSE repo. I don’t know what it is for and what it does affect, but it is KDE and so graphics related… (some time ago, I had a conversation with the maintainer of the Mozilla OBS repo at openSUSE, he told me, that his patch is included since a long time and should be reviewed at some time — well…) (you could try FlatPak or Snap at last because they are other compiles than the RPM in repo)

[C7NhtpnK]

Maybe for further troubleshooting, you should tell:

• what Firefox: RPM (which version, which repo=? Or Flatpak? Or Snap? (try Flatpak or Snap, at least just for troubleshooting, they are other compiles)
• windows manager: X or Wayland? (try X)
• desktop manager: KDE, Gnome, Xfce or what ever? (try Xfce or something other than KDE nor Gnome)
• graphics: AMD, Nvidia, Intel? and what drivers? (try standard drivers, try internal graphics than dedicated graphics)
• Firefox settings: recommended performance settings (try setting off)
• Firefox settings: hardware acceleration (try setting off)

[heitormoreira]

@C7NhtpnK

what Firefox: RPM (which version, which repo=? Or Flatpak? Or Snap? (try Flatpak or Snap, at least just for troubleshooting, they are other compiles)

It’s already here.

@pilotgi

openSUSE Paste

[pilotgi]

I’ve been using X for the last several hours and there’s been no Firefox crashes. Maybe the “Wayland protocol error” that I posted above is the culprit. Starting Firefox from Konsole was a helpful tip.

[pilotgi]

After the Plasma 6.1.2 bug fix, Firefox in Wayland hasn’t crashed all morning. Scrolling and the mouse cursor are also faster.

[pilotgi]

I spoke too soon with my previous post. Firefox is still crashing when I’m in a Wayland session. I sent some crash reports to Mozilla bugs but I haven’t heard anything back from them.