Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

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

  • 2 Antworten
  • 6 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von 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.

Alle Antworten (2)

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:

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"?