Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Learn More

Segfault on startup after upgrading to version 24.

  • 3 respostas
  • 13 têm este problema
  • 1 visualização
  • Última resposta de 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.

Alterado por cor-el em

Todas as respostas (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?