Interacting With / Clicking On / Click On Any Extension Crashes Linux Firefox | 147.0.2 (64-bit) Debian 12 Gnome Wayland
NB - For the past half a year I have to sometimes right click to interact with them, anyway
Effectively, I will interact with the extension at the most basic, normal level on something that has interactive elements like a dropdown menu, or basic options.
I will click / right click on the icon and the highlight will appear, then that's it ... the browser then crashes and does not recover. :(
What's worse is that I have to Force Quit and when I restart there is no crash report to send to Moz.
I am just wondering if other Linux users have experienced similar issues.
The attached image is taken at the moment before the 'Force Quit' dialogue opens up in Debian 12 Gnome (Wayland) ...
I have Hardware Acceleration on.
I am about to start testing with it off, but I work from the browser, and do not want performance compromises. So that is (at best) a work-around, and certainly is not a fix.
I'm on version 147.0.2 (64-bit) which would appear to be from the Mozilla Firefox Debian Package mozilla-deb - 1.0 install/repo/whatever ... and the PC specs are: Processor: Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz Memory: 32705MB (11893MB used) Resolution: 7680x2358 pixels OpenGL Renderer: Quadro RTX 3000/PCIe/SSE2
These are my media. prefs ... but ... I doubt that it is relevant: media.ffmpeg.allow-openh264 true media.ffmpeg.customized-buffer-allocation true media.ffmpeg.disable-software-fallback false media.ffmpeg.enabled true media.ffmpeg.encoder.cpu-used 7 media.ffmpeg.encoder.enabled true media.ffmpeg.encoder.quantizer-max 35 media.ffmpeg.encoder.quantizer-min 10 media.ffmpeg.vaapi.force-surface-zero-copy 2
Modifié le
Toutes les réponses (4)
So you're saying that when you click on any of the extensions you have installed the browser goes BOOM? What happens when using X11? I'm not seeing these issue on my laptops running Leap(1) and Tumbleweed(3). Have you tried using a tarball from Mozilla to see if you have the same issues?
Modifié le
Hi, @jonzn4SUS , thanks for your interest in this as a fellow non-mozilla employee! :-)
- Not going to get into a Wayland/X11 thing
- I will try this
- No idea what those are, but I am happy for you :-)
- The only means of install on this Debian are official Deb / Moz repos ... not really sure what I would do with a tarball and do not have the time / ability to learn something new to test an issue that I have seen
For further context, this is a work PC, designed to be as by the book as possible on stable Deb 12. :-)
So, for it is impossible to test this in Troubleshoot mode as you cannot test tapping on extensions, when the very nature of Troubleshoot mode disables the thing that you need to tap on.
I have tried to gather a BIT more data from the Browser Toolbox, and the last thing to flash up there, when I set it to record in the 'Debugging' profile was:
data:application/json,{"payload":{"permissions":{"capabilities":["script","object","media","frame","font","webgl","fetch"],"temp":false}}}
The above seems to occur whenever one taps an extension icon in the UI. So ... it is possible that this is a WebGL thing.
Additionally, there are a number of errors around the below, repeating:
WebExtension context not found! 2 ExtensionParent.sys.mjs:1364:13
getContextById resource://gre/modules/ExtensionParent.sys.mjs:1364
recvRemoveListener resource://gre/modules/ExtensionParent.sys.mjs:1343
_recv resource://gre/modules/ConduitsChild.sys.mjs:90
receiveMessage resource://gre/modules/ConduitsParent.sys.mjs:474
Modifié le
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted (and Unsubmitted, if any) Crash Reports will appear, similar to the one shown below.
- Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.