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!

Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

CPU jumps to 50% when exiting Firefox, then stays there. Why?

  • 2 odpowiedzi
  • 6 osób ma ten problem
  • 3 wyświetlenia
  • Ostatnia odpowiedź od hysan

hysan
hysan
more options

I am using WinXP and Firefox 26.0. 4GB RAM

From looking at Windows Task Manager I came to realise that Firefox continues to run after Exit. It NEVER closes, and continues to use 50% of CPU. Needed to use End Process.

Then, watching Windows Task Manager some more I discovered that the process was NOT using that CPU while running. Only after Exit did the CPU usage suddenly jump to 50%, and stay there. Only End Process closes Firefox.exe.

Any help or advice appreciated.

I am using WinXP and Firefox 26.0. 4GB RAM From looking at Windows Task Manager I came to realise that Firefox continues to run after Exit. It NEVER closes, and continues to use 50% of CPU. Needed to use End Process. Then, watching Windows Task Manager some more I discovered that the process was NOT using that CPU while running. Only after Exit did the CPU usage suddenly jump to 50%, and stay there. Only End Process closes Firefox.exe. Any help or advice appreciated.

Wszystkie odpowiedzi (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Use "Firefox > Exit" (Windows: Firefox/File > Exit; Mac: Firefox > Quit Firefox; Linux: Firefox/File > Quit) to close Firefox if you are currently doing that by clicking the close X on the Firefox title bar.

See:

hysan
hysan Zadający pytanie
more options

Thanks. But I was already using Exit (rather than clicking the close X), having already read that advice on earlier complaints about similar problems.

Any "next thing to try"?