firefox crashes on launch after upgrading to 146.0-1 (solved)

mayu · 2025-12-10 20:44:03

I just upgraded firefox from 145.0.2-1 to 146.0-1 along with a number of other packages using pacman -Syu, and now it crashes on launch with an error:

kernel: NVRM: VM: invalid mmap

Starting firefox normally with no arguments causes it to crash.
Starting the firefox profile switcher also crashes.
Launching into a profile directly with firefox -P "myprofile" does not crash, this works as expected.

I reverted firefox back to its previous version 145.0.2-1 and everything works normally again.

Does anyone have any advice for how to investigate this further?
Thanks

Last edited by mayu (2025-12-11 00:08:53)

jsov · 2025-12-10 20:49:57

Hi! Does running

$ firefox --safe-mode

fix anything?

Additionally, we can try
1. Rebooting
2. Removing the firefox cache:

$ rm -rf ~/.cache/mozilla/firefox

3. checking

# pacman -Qkk firefox

to see if any files are missing
4. Check about:support for crash data - if none is there, try about:crashes.
5. Check

 journalctl -b

for anything related to firefox

Last edited by jsov (2025-12-10 20:58:02)

mayu · 2025-12-10 20:57:10

Thanks for your reply. Running with --safe-mode doesn't seem to change anything, I get the same crash.
I should add that I've rebooted after the initial package upgrade.

jsov · 2025-12-10 20:59:06

Gotcha. I edited my first reply with a few other things to check - you responded so fast I didn't have a chance to get my edit in time!

mayu · 2025-12-10 21:03:40

Removing the cache doesn't seem to have had an effect.

"pacman -Qkk firefox" returns this:
firefox: 98 total files, 0 altered files

about:support doesn't say anything about the crashes, but about:crashes does have some crash dumps on it.

journalctl -b just shows that kernel error message that I pasted in the first post. It prints that line something like 10 times every time I try to run the program.

jsov · 2025-12-10 21:10:04

Which Nvidia driver, version, and card are you using? Also, have you noticed any other issues with your GPU?

Additionally, what is your desktop environment or window manager, and are you running it with Xorg or Wayland?

Last edited by jsov (2025-12-10 21:15:35)

seth · 2025-12-10 21:21:17

Launching into a profile directly with firefox -P "myprofile" does not crash, this works as expected.

Either there's a stale FF process ("ps aux | grep firef", selecting a profile launches a new instance) or there's a problem w/ the default profile, see ~/.mozilla/firefox/ and https://wiki.archlinux.org/title/Firefo … ox_refresh - but I'm not sure how we'd address the bogus profile if you cannot launch FF.
Maybe refreshing it w/ 145 is enough?
Alternatively try to move aside ~/.mozilla/firefox/*/prefs.js (pick the reelvant profile) in case it's some local setting.

jsov · 2025-12-10 21:28:25

seth wrote:

Either there's a stale FF process ("ps aux | grep firef", selecting a profile launches a new instance)

Would this stale process persist across reboots?

seth · 2025-12-10 21:31:37

Auto(re)start on session login might be a factor, but mostly those are the two options for why explicitly selecting a profile works but the default profile doesn't.
Any why believe if you get to peek?

mayu · 2025-12-10 21:35:27

Driver is 580.105.08, card is RTX 4080 SUPER. I haven't noticed any gpu or video related problems with anything else.
No stale firefox processes.
I backed up and deleted all of my profiles, the crash still occurs using a new profile created from 145.

seth · 2025-12-10 21:37:39

I backed up and deleted all of my profiles, the crash still occurs using a new profile created from 145.

So

firefox -P "myprofile"

now crashes as well??

jsov · 2025-12-10 21:40:03

mayu wrote:

Driver is 580.105.08

Is this the nvidia package or the nvidia-open package?

mayu · 2025-12-10 21:41:30

Sorry, I meant to say that the same problem continues to happen.
With only one fresh "myprofile", it crashes with either `firefox` or `firefox -P` but `firefox -P "myprofile"` does work.

mayu · 2025-12-10 21:43:06

jsov wrote:

mayu wrote:
Driver is 580.105.08
Is this the nvidia package or the nvidia-open package?

That's what nvidia-smi says next to "Driver version".

Pacman says this:

$ pacman -Q | grep nvidia
lib32-nvidia-utils 580.105.08-1
libnvidia-container 1.18.1-1
libva-nvidia-driver 0.0.14-1
linux-firmware-nvidia 20251125-2
nvidia-container-toolkit 1.18.1-1
nvidia-open-dkms 580.105.08-5
nvidia-utils 580.105.08-5

jsov · 2025-12-10 21:44:09

mayu wrote:

nvidia-open-dkms 580.105.08-5

yep, you're using the right version! just checking, that's caused a lot of confusion before.

seth · 2025-12-10 21:47:54

With only one fresh "myprofile", it crashes with either `firefox` or `firefox -P` but `firefox -P "myprofile"` does work.

Can we please see the coredump?

Also also a complete system journal

sudo journalctl -b | curl -F 'file=@-' 0x0.st

a) so we're not guessing the HW/drivers
b) "kernel: NVRM: VM: invalid mmap" rarely comes alone, there's usually an entire kernel backtrace attached to that

mayu · 2025-12-10 22:55:46

I wasn't able to find a core dump with "coredumpctl list".
I tried running firefox in gdb and I got this weird huge stack trace.

https://0x0.st/KCHb.txt

I'm on hyprland. I just tried the below command, it does not crash when this is set to 0.

MOZ_ENABLE_WAYLAND=0 firefox

I don't know if I want to upload the entire journal, in "journalctl -b" it just shows a bunch of these "invalid mmap" lines every time I reproduce the crash. Below is the output for one attempt to launch firefox, with one line of context on both ends.

Dec 10 17:36:22 myarch systemd[1]: Started Time & Date Service.
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:30 myarch kernel: NVRM: VM: invalid mmap
Dec 10 17:36:53 myarch rtkit-daemon[941]: Supervising 10 threads of 5 processes of 1 users.

Should I report this somewhere else, like to hyprland?

If I change my display scaling in hyprland.conf from 1.33 to 1, it stops crashing.
It seems that the profile selector window crashes when my scale is set to 1.33 and MOZ_ENABLE_WAYLAND is 1 and only on firefox-146.

Last edited by mayu (2025-12-10 23:07:07)

seth · 2025-12-10 23:16:38

#18 0x00007fffafcb526a in mozilla::AppWindow::Center (this=0x7fffa2c56360, aRelative=0x0, aScreen=true, aAlert=false) at /usr/src/debug/firefox/firefox-146.0/xpfe/appshell/AppWindow.cpp:824
…
#43614 0x00007fffafcb526a in mozilla::AppWindow::Center (this=0x7fffa2c56360, aRelative=0x0, aScreen=true, aAlert=false) at /usr/src/debug/firefox/firefox-146.0/xpfe/appshell/AppWindow.cpp:824

looks like FF is recursing in the function and looks like it's https://bugzilla.mozilla.org/show_bug.cgi?id=1998188
Profile selection also fits, https://bugzilla.mozilla.org/show_bug.c … 998188#c13

NVRM: VM: invalid mmap might be a red herring/consequence because of the overallocation - you don't get that w/ 145 ?

mayu · 2025-12-10 23:33:35

seth wrote:

NVRM: VM: invalid mmap might be a red herring/consequence because of the overallocation - you don't get that w/ 145 ?

No, I only get the mmap lines when it crashes, which only happens on 146.
I will wait for these bug fixes to make their way to me. Thanks for helping me investigate this issue.

seth · 2025-12-10 23:38:49

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

firewalker · 2025-12-14 07:43:55

146.0-1 crashes for me at startup for me when primary password is enable. If I start with a clean profile it is ok. Upon enabling primary password it will crash every time upon starting. Is it related?

Alexander.

seth · 2025-12-14 08:58:40

Probably not.
The bug affected the (new) profile selection dialog - it matters if you manually pass a profile, but not which.

There's a mesa related bug, https://bbs.archlinux.org/viewtopic.php?id=310943 but not a startup.
Check your system journal - it'll probably relate to your local secrets service (kwallet, gnome-keyring, stuff like that) and in doubt open a new thread and provide some data on the situation (shell output, crash dump, journal, … etc)

Arch Linux

#1 2025-12-10 20:44:03

firefox crashes on launch after upgrading to 146.0-1 (solved)

#2 2025-12-10 20:49:57

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#3 2025-12-10 20:57:10

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#4 2025-12-10 20:59:06

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#5 2025-12-10 21:03:40

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#6 2025-12-10 21:10:04

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#7 2025-12-10 21:21:17

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#8 2025-12-10 21:28:25

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#9 2025-12-10 21:31:37

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#10 2025-12-10 21:35:27

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#11 2025-12-10 21:37:39

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#12 2025-12-10 21:40:03

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#13 2025-12-10 21:41:30

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#14 2025-12-10 21:43:06

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#15 2025-12-10 21:44:09

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#16 2025-12-10 21:47:54

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#17 2025-12-10 22:55:46

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#18 2025-12-10 23:16:38

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#19 2025-12-10 23:33:35

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#20 2025-12-10 23:38:49

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#21 2025-12-14 07:43:55

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

#22 2025-12-14 08:58:40

Re: firefox crashes on launch after upgrading to 146.0-1 (solved)

Board footer