Fresh Firefox crashes, but not in safe mode

My Firefox has been crashing for a few days, and if I’m not wrong, it’s getting more frequent. It doesn’t crash in safe mode, but when I use the feature that makes it “fresh,” it crashes again, even if I don’t make any changes to the fresh version.

When I checked the differences between fresh and safe mode, the only thing I could find was hardware acceleration. So, I created a new “fresh” version with only one change in the setting to turn off hardware acceleration. It still crashes.

Does anyone have any idea how to fix this issue?

Search the journal for the crashes so you can see why it is crashing.

I run this:

journalctl --since yesterday --case-sensitive=false --grep firefox

But it doesn’t give me anything related to Firefox. Am I missing something?

If you create a temporary account to your system, does firefox crash on that?

Now that you mentioned, I remembered that my messaging web applications are opened in a different Firefox profile, and they don’t crash. I’m going to open LinkedIn and similar applications that crash the main profile in that second profile to see what happens, and then as you suggested, I’ll try it with a temporary account in my OS.

It will take a little time to test any of these, because it doesn’t crash immediately and I have to keep working using it to get, on average, one crash every 20 minutes or so.

Since firefox writes a log when it starts, that seems pretty strange.

How did you install firefox?

It’s from the “extra” repo (version 130.0-1).

So, using the alternative Firefox profile didn’t work. It hadn’t crash with the messaging applications that I normally open in it, but LinkedIn made it crash.

Could be some setting related to LinkedIn, like (not) allowing cookies etc.?

LinkedIn is not the only one. I think it happens more with websites that have heavy javascript.

How does it crash? I lately have the issue that it kinda “freezes” i can open other apps and things just fine… Nothing happens… it just seems like firefox is kinda “stuck” if i do nothing it unfreeze itself after some seconds. So it doesn’t seem to really crash. it only seems to happen when my mouse cursor is a “hand” for whatever reason. So i guess some bug or something gets triggered. I also don’t find anything related to it in the Journal.

1 Like

In crashes in that the application is closed [and loaded after getting a confirmation from me] and a crash report is generated. When loaded again, it can open the previous tabs as well.

In this case, run firefox from a terminal. When it crashes, there will be some output in the terminal

Thanks for the tip. Here’s the output:

Missing chrome or resource URL: chrome://browser/skin/aboutSessionRestore-window-icon.png
Missing chrome or resource URL: chrome://browser/skin/abyss/img/waterfox-abyss-preview.svg
Missing chrome or resource URL: chrome://browser/skin/aboutSessionRestore-window-icon.png
Missing chrome or resource URL: chrome://browser/skin/abyss/img/waterfox-abyss-preview.svg
Missing chrome or resource URL: chrome://browser/skin/aboutSessionRestore-window-icon.png
Missing chrome or resource URL: chrome://browser/skin/abyss/img/waterfox-abyss-preview.svg
ExceptionHandler::GenerateDump attempting to generate:/home/nader/.mozilla/firefox/0n0ekbcu.NaNormal/minidumps/6c9a562b-a565-c012-989a-3231a9186176.dmp
ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal…
1405896
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::GenerateDump minidump generation succeeded
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.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.

JournalCtl grep does not work like command grep.
You should better use a terminal window and let journalctl -f running, while starting firefox as usual.

Also, is it really :copyright: Firefox, or something else?

I don’t know what that missing waterfox is about; it’s a normal Firefox.

I did as you said, and I got the following around the time it crashed:

pcieport 0000:00:03.0: AER: Corrected error message received from 0000:01:00.0
nvidia 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
nvidia 0000:01:00.0: device [10de:1b80] error status/mask=00001000/0000a000
nvidia 0000:01:00.0: [12] Timeout

Is it the problem?

If you’ve used Waterfox before and reused the config folder, but under base Firefox, it may be the reason for that waterfox error.

On that note, could you check if this happens with an empty .mozilla folder?

  • Close Firefox
  • Make a backup of your .mozilla folder
  • Relaunch Firefox and use it for a while to see if it crashes or not

Normally, creating a new Firefox profile should be enough, but it shouldn’t have any issues if there is no data at all to read.

I just tried it with am empty .mozilla directory, and it crashed again.

@manuel had suggested that you should create a temporary user account for your system. To be clear, I think he meant a new username for EndeavourOS, not a Firefox profile.

Have you done this?

If not, please try it.

Also, is this happening on Wayland and X11 or only one? Have you tested this?

It also crashes in the new OS user account that I’ve built.

The only scenario in which it doesn’t crash is “safe mode”.

This happens in X11. I don’t have Wayland on this computer.