[SOLVED] Firefox 89.0.1 segmentation fault on slarm64?

shelldweller · 06-20-2021, 06:39 AM

After upgrading to mozilla-firefox-89.0.1-aarch64-1, it no longer launches and instead spits out a "Segmentation fault". Is anyone else getting this? It is happening on all of my slarm64 machines that have firefox installed. I thought I would just check in to see if anyone else is experiencing this before I try to reset the user profile, etc.

thanks much.

sndwvs · 06-20-2021, 07:18 AM

Quote:

Originally Posted by shelldweller

After upgrading to mozilla-firefox-89.0.1-aarch64-1, it no longer launches and instead spits out a "Segmentation fault". Is anyone else getting this? It is happening on all of my slarm64 machines that have firefox installed. I thought I would just check in to see if anyone else is experiencing this before I try to reset the user profile, etc.

thanks much.

did not observe such problems and communicating with another user after the update also works, without resetting the profile.

also worth looking at

Code:

strace firefox

shelldweller · 06-20-2021, 09:57 PM

Ok, that is interesting to know, thank you. I have tried creating a new user, using a different DE, refreshing the profile, creating a new profile, etc. This is consistently happening on a Raspberry Pi 4 (legacy kernel) and a Pinebook (legacy kernel) no matter what the environment is like.

This is the error message:

Code:

bash-5.1$ firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI (t=7.29735) [GFX1-]: No GPUs detected via PCI

###!!! [Parent][MessageChannel] Error: (msgtype=0x39015D,name=PContent::Msg_CommitWindowContextTransaction) Channel error: cannot send/recv


###!!! [Parent][MessageChannel] Error: (msgtype=0x39015D,name=PContent::Msg_CommitWindowContextTransaction) Channel error: cannot send/recv

Exiting due to channel error.
Segmentation fault
Exiting due to channel error.
Exiting due to channel error.
bash-5.1$

I have tried to eliminate any obvious variable such as GTK theme, desktop environment, add-ons, browser themes, etc. I will try a fresh image on an SD card to see if it happens there. So far it is pretty consistent. Like I said, even a fresh profile with a brand new user gives the same output.

The strace suggestion almost worked. It spits out the same errors above plus a lot of other stuff that is not an error, just sys calls. But it gave me the idea to try:

Code:

 firefox --safe-mode

which actually works fine without crashing and gives me access to my bookmarks and saved passwords. No other option I tried prevented the browser from crashing (even --headless). Only safe-mode does the trick, so far. I will report back if I notice anything interesting on a fresh SD card image.

Thanks for the feedback in any case, it helps me troubleshoot.

sndwvs · 06-20-2021, 10:15 PM

which version of mesa?

Code:

# glxinfo | grep -i mesa
    GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
client glx vendor string: Mesa Project and SGI
    GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, 
    GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, 
    GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, 
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa/X.org (0xffffffff)
OpenGL vendor string: Mesa/X.org
OpenGL core profile version string: 4.5 (Core Profile) Mesa 21.1.2
    GL_KHR_texture_compression_astc_sliced_3d, GL_MESA_framebuffer_flip_y, 
    GL_MESA_pack_invert, GL_MESA_shader_integer_functions, 
    GL_MESA_texture_signed_rgba, GL_MESA_ycbcr_texture, 
OpenGL version string: 3.1 Mesa 21.1.2
    GL_KHR_texture_compression_astc_sliced_3d, GL_MESA_pack_invert, 
    GL_MESA_shader_integer_functions, GL_MESA_texture_signed_rgba, 
    GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, 
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.1.2
    GL_KHR_texture_compression_astc_sliced_3d, GL_MESA_framebuffer_flip_y, 
    GL_MESA_shader_integer_functions, GL_NV_conditional_render,

shelldweller · 06-21-2021, 10:33 PM

Quote:

Originally Posted by sndwvs

which version of mesa?

Here is my corresponding output. Note that mesa recently updated, and the problem was happening before that update, and is still happening.

Code:

bash-5.1# glxinfo | grep -i mesa
    GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, 
client glx vendor string: Mesa Project and SGI
    GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, 
    GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, GLX_MESA_swap_control, 
Extended renderer info (GLX_MESA_query_renderer):
OpenGL version string: 2.1 Mesa 21.1.3
    GL_KHR_texture_compression_astc_sliced_3d, GL_MESA_pack_invert, 
    GL_MESA_tile_raster_order, GL_MESA_window_pos, GL_NV_blend_square, 
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 21.1.3
    GL_KHR_texture_compression_astc_sliced_3d, GL_MESA_tile_raster_order,

I was able to narrow it down to the last Firefox update. I have an SD image created on 2021-06-17 (with an enlightenment DE, just for reference) that has Firefox 89.0 installed, as well as mesa 21.1.2. Before updating anything on that image, Firefox works fine. This is on a Pinebook (although I can reproduce it on a Raspberry Pi 4). I then run a slackpkg update (after grabbing the GPG-KEY from a repository using wget, this was not pre-installed in the image for some reason) and allow only Firefox to update to 89.0.1 (skipping everything else, including mesa). Now Firefox segfaults like it does on my other systems. Then I went ahead and updated everything else, including mesa to 21.1.3, but that does not help the Firefox issue, sadly.

Historically, from what I can find around the web, this seems to crop up from time to time over the years on different platforms and seems to be processor-specific, even in the x86 world, from what I gather from the forums. The symptoms are the random crash shortly after launching with a segmentation fault, while working in safe-mode avoids the problem somehow, despite not having any add-ons installed in the other mode. Eventually an upgrade to the next version makes the problem go away. I am guessing/hoping that this is a similar instance. It might just go away with the next update.

Since I only use Firefox for a few sites (banking and such, sites that complain if you are not using Firefox or Chrome specifically), and I use SeaMonkey and/or text browsers for everything else. the safe-mode workaround actually does not bother me that much for the time being.

The strange part is that when I launch Firefox 89.0 from the command line on the fresh unaltered enlightenment image, I get the same errors I listed above, minus the "segmentation fault". Everything else that 89.0.1 complains about is also present in the output of 89.0, with the one exception of "segmentation fault". So all the other error messages are probably completely unrelated to this issue.

UPDATE: I was able to grab a full strace output this time (capture was not working for me the other day, not sure why, might have been tired...). The raw text is somewhat large. I uploaded a gzipped version of it as well for quicker downloading.

https://shelldweller.beauxbead.com/s...ce_firefox.txt

https://shelldweller.beauxbead.com/s...firefox.txt.gz

thanks again.

shelldweller · 06-26-2021, 11:59 AM

Upgrading to verision 89.0.2 completely fixed the issue. Marking this as solved, thanks again for helping me troubleshoot.

sndwvs · 06-26-2021, 12:07 PM

good news