We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Segfault on startup after upgrading to version 24.

  • 3 replies
  • 13 have this problem
  • 1 view
  • Last reply by raamee

more options

When I try to start firefox (even in safe mode), I always get this terminal output:

andrey@hub:~$ firefox
###!!! ABORT: OOM: file /build/buildd/firefox-24.0+build1/xpcom/string/src/nsReadableUtils.cpp, line 160
###!!! ABORT: OOM: file /build/buildd/firefox-24.0+build1/xpcom/string/src/nsReadableUtils.cpp, line 160
Segmentation fault (core dumped)

and it crashes. I tried googling the issue but came up blank.

When I try to start firefox (even in safe mode), I always get this terminal output: <pre><nowiki>andrey@hub:~$ firefox ###!!! ABORT: OOM: file /build/buildd/firefox-24.0+build1/xpcom/string/src/nsReadableUtils.cpp, line 160 ###!!! ABORT: OOM: file /build/buildd/firefox-24.0+build1/xpcom/string/src/nsReadableUtils.cpp, line 160 Segmentation fault (core dumped)</nowiki></pre> and it crashes. I tried googling the issue but came up blank.

Modified by cor-el

All Replies (3)

more options

Could it be possible that the full path to some of the files is too long?

You can try to delete the ~/.mozilla/firefox folder. You can make a backup of your personal data in the profile folder before doing this.

You can also try to do a clean reinstall of Firefox.

more options

The absolute last thing I want to do is configure all my extensions again, especially since I have some pretty important data saved in there. I'd rather solve the issue instead of reinstalling firefox..

How do I make the path shorter? Are there any other approaches I can try? Is downgrading a viable option?

more options

I have the same issue and tried your suggestion but still the error persists. I even re-installed the OS but I get the same error. What could be the solution?