What Desktop? X11 or Wayland?

Have you tried with Firefox in Troubleshoot Mode? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#w_how-to-start-firefox-in-4troubleshoot-modesf5safe-modesf

Try downloading Firefox from Mozilla, run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

Operating System: openSUSE Tumbleweed 20251121 KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.0 Kernel Version: 6.17.8-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics Memory: 64 GiB of RAM (62.1 GiB usable) Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP ProBook 455 15.6 inch G9 Notebook PC

Hi Keith, I couldn't find that report on https://crash-stats.mozilla.org/.

If you have access, could you check the about:crashes page, Submitted Crash Reports section, to see whether the report ID has been updated with a bp- prefixed ID?

sorry jscher, i put a number that had not been submitted yet.. here is the most recent one that was submitted bp-e82a0ef7-c438-4844-8748-37e580251123

Hi Keith, I couldn't find that report on https://crash-stats.mozilla.org/. If you have access, could you check the about:crashes page, Submitted Crash Reports section, to see whether the report ID has been updated with a bp- prefixed ID?

sorry jscher, i put a number that had not been submitted yet.. here is the most recent one that was submitted bp-e82a0ef7-c438-4844-8748-37e580251123

What Desktop? X11 or Wayland? Have you tried with Firefox in Troubleshoot Mode? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#w_how-to-start-firefox-in-4troubleshoot-modesf5safe-modesf Try downloading Firefox from Mozilla, run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release Operating System: openSUSE Tumbleweed 20251121 KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.0 Kernel Version: 6.17.8-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics Memory: 64 GiB of RAM (62.1 GiB usable) Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP ProBook 455 15.6 inch G9 Notebook PC

hi.. its running X, no i was not aware of that.. i will try troubleshooting mode.. and, if i download the executable, wont that be like deleting all the stored session files and or profiles? like deleting .mozilla? id assume if i did that right now the problem would be gone. thanks

No, the file will just run and it's not installed, just running from the folder. I run several versions of Firefox and Waterfox from my download folder via shortcuts on the desktop. see screenshot

The crash signature (.plt ELF section in libxul.so) appears to be novel -- the More Reports link shows only 2 crashes with the same signature in the past month, perhaps both on your Firefox. I have no idea what it means, unfortunately.

Do other crash reports have different signatures?

You should not have to delete any profile data to run a different executable, but after Firefox 145.0.1 runs your profile, Firefox 144.0.2 probably will not want to "downgrade" it.

The crash signature (.plt ELF section in libxul.so) appears to be novel -- the More Reports link shows only 2 crashes with the same signature in the past month, perhaps both on your Firefox. I have no idea what it means, unfortunately. Do other crash reports have different signatures? You should not have to delete any profile data to run a different executable, but after Firefox 145.0.1 runs your profile, Firefox 144.0.2 probably will not want to "downgrade" it.

ok here are the others.. they should be for the same issue

bp-d7ecd313-7778-436f-9203-0e4d60251124 11/24/25, 09:05

bp-fe36ea98-df87-47fa-933b-4af5c0251124 11/24/25, 09:05

bp-6b9b67b9-144f-4328-a6e1-e7f970251124 11/24/25, 09:05

bp-53c915c6-8860-40a1-a535-704190251124 11/24/25, 09:05

What's the result when in Troubleshoot mode? You can also run strace to see what happens. strace -t -o firefox_debug.txt firefox & The 2nd screenshot shows why the browser closed in the output file firefox_debug.txt.

https://wizardzines.com/zines/strace/

Hi Keith, thank you for the additional crash reports. Two of them are for the same signature (".plt ELF section in libxul.so") and two are different:

(1) bp-fe36ea98-df87-47fa-933b-4af5c0251124 => "GetSelectionClosestFrameForChild"

This one also is unique in the last month, so no clues there, except that it definitely refers to finding what you selected.

(2) bp-6b9b67b9-144f-4328-a6e1-e7f970251124 => "Mutex::Unlock"

There are 99 reports of this on Windows (63), Linux (32), and Mac (1) during the past month. Most are in Firefox 144-145 (57), but also in beta versions (7) and older versions (35). It probably is due to a bug caused by failing to release memory, but there isn't any obvious indication of how to work around it.

Since these crashes are relatively rare, I wonder whether the issue could be:

(A) Visiting a particular website which is attempting to exploit browsers. Do you notice any pattern with the involved websites?

(B) A problem extension. Troubleshoot Mode disables all extensions, so this is a fair test of whether one of them might be the culprit.

(C) A physical memory issue. Sometimes random crashes are due to a problem with memory that can be confirmed or ruled out with a memtest of some kind.

(D) External software tampering with browser memory, whether for "anti-exploit" or nefarious reasons.

Hi Keith, thank you for the additional crash reports. Two of them are for the same signature (".plt ELF section in libxul.so") and two are different: (1) bp-fe36ea98-df87-47fa-933b-4af5c0251124 => "GetSelectionClosestFrameForChild" This one also is unique in the last month, so no clues there, except that it definitely refers to finding what you selected. (2) bp-6b9b67b9-144f-4328-a6e1-e7f970251124 => "Mutex::Unlock" There are 99 reports of this on Windows (63), Linux (32), and Mac (1) during the past month. Most are in Firefox 144-145 (57), but also in beta versions (7) and older versions (35). It probably is due to a bug caused by failing to release memory, but there isn't any obvious indication of how to work around it.

---

Since these crashes are relatively rare, I wonder whether the issue could be:

(A) Visiting a particular website which is attempting to exploit browsers. Do you notice any pattern with the involved websites?

(B) A problem extension. Troubleshoot Mode disables all extensions, so this is a fair test of whether one of them might be the culprit.

(C) A physical memory issue. Sometimes random crashes are due to a problem with memory that can be confirmed or ruled out with a memtest of some kind.

(D) External software tampering with browser memory, whether for "anti-exploit" or nefarious reasons.

interestingly, i just replaced a DIMM cuz it failed a mem test.. now the laptop has more memory.. its my wifes laptop so ill try the executable downloaded version and also trouble shooting mode. i was surprised because she said it was happening every time then i finally sat down to look at it, when i remote desktop in and selected text, it didnt crash.. go figure.

What's the result when in Troubleshoot mode? You can also run strace to see what happens. strace -t -o firefox_debug.txt firefox & The 2nd screenshot shows why the browser closed in the output file firefox_debug.txt. https://wizardzines.com/zines/strace/

ill try that soon and thanks for the strace . ill try that and check the txt file after the fact if it goes down.