Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

ابحث في الدعم

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

This thread was archived. Please ask a new question if you need help.

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

  • 2 (ردّان اثنان)
  • 6 have this problem
  • 1 view
  • آخر ردّ كتبه 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.

All Replies (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 صاحب السؤال
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"?