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”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Firefox consistently monopolises 99% CPU -- even after fixes suggested on Support pages (deactivate add-ons, run in Safemode, reinstall) (XP, 2GB)

  • 21 respostas
  • 9 têm este problema
  • 2 visualizações
  • Última resposta de rutherford2017

more options

Firefox consistently monopolises 99% of memory -- except, inexplicably, whenever I am on a Mozilla Support page. (I usually have three or four tabs open: hotmail, work email, Linkedin and theguardian newspaper. When I am 'on' any of these pages, Firefox usage is 94-99%; if I open a Mozill Support page, when I am 'on' this page, usage drops below 10%.)

I have tried all of the solutions suggested on the Support site (disabled all add-ons, run in Safe mode, re-installed latest version) but all to no avail. When left unattended for an hour or more, Firefox crashes, but is then "unable" to send a report. I use Windows XP.

Firefox consistently monopolises 99% of memory -- except, inexplicably, whenever I am on a Mozilla Support page. (I usually have three or four tabs open: hotmail, work email, Linkedin and theguardian newspaper. When I am 'on' any of these pages, Firefox usage is 94-99%; if I open a Mozill Support page, when I am 'on' this page, usage drops below 10%.) I have tried all of the solutions suggested on the Support site (disabled all add-ons, run in Safe mode, re-installed latest version) but all to no avail. When left unattended for an hour or more, Firefox crashes, but is then "unable" to send a report. I use Windows XP.

Alterado por Wayne Mery em

Todas as respostas (1)

more options

It crashes occasionally, but the most persistent problem is that, by monopolising 97-99% of the CPU, it makes the computer run REALLY slowly.

(Please be kind enough to remind me how to access crash IDs.)

  1. 1
  2. 2