Firefox crash after last update [Solved]

[hebelwirkung]

For what it's worth, I've been trying Firefox 110.0 in EndeavourOS and so far have experienced no crashes, including on pages which repeatedly crashed when running the browser in MX 21.3. Browser addons etc are identical in both systems. I have no idea what to make of this - just thought it worth reporting.

[Huckleberry Finn]

As Stevo already said: Just any user needs to issue:

Code: Select all

firefox

in a terminal then post the output when it crashes.

(More posts (outputs) from more users will be more helpful for devs.)

[hebelwirkung]

As Stevo already said: Just any user needs to issue:

Code: Select all

firefox

in a terminal then post the output when it crashes.

Okay, this is the terminal output relating to opening tumblr.com, followed by an almost instant crash:

[GFX1-]: glxtest: VA-API test failed: failed to initialise VAAPI connection.
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
firefox.real: ../../src/xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
ExceptionHandler::GenerateDump cloned child 8364
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.

Note - the same "failed to initialise VAAPI connection" message appears when starting Librewolf - a Firefox clone also upgraded to version 110 a few days ago - in a terminal. But there, similarities end. Librewolf does NOT crash, whereas Firefox 110 tirelessly does...

[bambuko]

...then post the output when it crashes...

mine doesn't crash (at least not as often as being reported here), but when started gets the same message about VAAPI as reported elsewhere...

Code: Select all

$ firefox
[GFX1-]: glxtest: VA-API test failed: no supported VAAPI profile found.
ATTENTION: default value of option mesa_glthread overridden by environment.

but.... when it crashes (this has happened after I have manually enabled VAAPI in about:config), this is the message:

Code: Select all

$ firefox
[GFX1-]: glxtest: VA-API test failed: no supported VAAPI profile found.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ExceptionHandler::GenerateDump cloned child 13494
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
bambuko@bambuko-mx:~
$ GConf Error: Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files

Failed to open curl lib from binary, use libcurl.so instead

[Eadwine Rose]

What happens when you disable hardware acceleration?

[bambuko]

Well... I have returned the settings back to as it was before and it is still running
If it fails I will report obviously, but it is interesting that things went pear shaped as soon as I started messing with:

Code: Select all

media.ffmpeg.vaapi.enabled
media.ffvpx.enabled
media.rdd-vpx.enabled
media.navigator.mediadatadecoder_vpx_enabled

BTW,

1-this is what is happening at the moment (while it is running fine):

Code: Select all

$ firefox
[GFX1-]: glxtest: VA-API test failed: no supported VAAPI profile found.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[2023-02-19T20:44:43Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2023-02-19T20:44:43Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2023-02-19T20:44:43Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2023-02-19T20:44:43Z ERROR mp4parse] Found 2 nul bytes in "\0\0"

2-changing hardware acceleration settings in Edit>Settngs>General doesn't make a blind bit of difference

[BitterTruth]

My problem is solved I think. I haven't had a crash all day after I changed this setting in firefox's about:config:

Code: Select all

gfx.canvas.accelerated                                 true                                                        =====> false

This was because the new release notes mention:

It's now possible to import bookmarks, history and passwords not only from Edge, Chrome or Safari but also from Opera, Opera GX, and Vivaldi for all the folks who want to move over to Firefox instead!

GPU sandboxing has been enabled on Windows.
Note: A bug in the popular X-Mouse Button Control (XMBC) tool may cause mouse wheel scrolling to stop working. The author(s) are working on an update. Meanwhile, scrolling can be restored by reconfiguring XMBC: either disable the Make scroll wheel scroll window under cursor option in the global settings, or enable the Disable scroll window under cursor option if using a custom profile for Firefox.

On Windows, third-party modules can now be blocked from injecting themselves into Firefox, which can be helpful if they are causing crashes or other undesirable behavior.

Date, time, and datetime-local input fields can now be cleared with Cmd+Backspaceand Cmd+Deleteshortcut on macOS and Ctrl+Backspaceand Ctrl+Deleteon Windows and Linux.

GPU-accelerated Canvas2D is enabled by default on macOS and Linux.

WebGL performance improvement on Windows, MacOS and Linux.

Enables overlay of hardware-decoded video with non-Intel GPUs on Windows 10/11, improving video playback performance and video scaling quality.[/list]

Yesterday, I was wrongly chasing 'gpu sandboxing' but that has been enabled since Firefox 109 at least and I had no problems with FF 109. If you want to disable it you can change this setting:

Code: Select all

security.sandbox.gpu.level                                   to '0' (zero)          

Mine was already set to '0'. Also disabling hardware acceleration had no effect. DISABLING THE GPU-ACCELERATED CANVAS2D SETTING WORKED.

[bambuko]

That is very interesting @BitterTruth
I have checked my gfx.canvas.accelerated and it is/was set to=true
so maybe this is why I never really had any problems?

[BitterTruth]

I think it might be because your on a different graphic driver to the rest of us (@dema2, @mike lovin, @pianokeyjoe) are all using:

OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5

I am using:

OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 18.3.6 direct render: Yes

You are using:

OpenGL: renderer: NV168 v: 4.3 Mesa 22.0.5 direct render: Yes

I have to say one of my machines is using the same driver as (@dema2, @mike lovin, @pianokeyjoe) and it has no problems. Not even with gfx.canvas.accelerated = true

COULD IT BE THE INTEL IRONLAKE CPU GRAPHICS AT FAULT HERE in combination with xfce4's compositor which apparently also does 2d hardware accelaration when enabled?

[Huckleberry Finn]

Inspector Clouseau :

It may be due to Mesa version:

Code: Select all

dema2		Mesa 20.3.5

pianokeyjoe	Mesa 20.3.5  (MX 19)

mike lovin      Mesa 20.3.5  (MX 19)

BitterTruth	Mesa 18.3.6  (MX 19)


BitterTruth	Mesa 20.3.5	(no issues)

bambuko	        Mesa 22.0.5	(better now, he says)