Avatar for Username

Søg i Support

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.

Læs mere

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

Firefox uses up 50% of my cpu after it has been closed for prolonged amounts of time.

  • 3 svar
  • 21 har dette problem
  • 14 visninger
  • Seneste svar af cor-el

AnonymousUser
AnonymousUser
more options

During when firefox is open and after it is closed it uses 50% of our cpu usage. This is seen by using the Task Manager. Also sometimes there is more then 1 entry of firefox using 50% of the cpu usage EACH. What is firefox doing when it is using so much of the cpu aafter it is clased and how do I stop it?

This happened

Every time Firefox opened

== I'm not sure

During when firefox is open and after it is closed it uses 50% of our cpu usage. This is seen by using the Task Manager. Also sometimes there is more then 1 entry of firefox using 50% of the cpu usage EACH. What is firefox doing when it is using so much of the cpu aafter it is clased and how do I stop it? == This happened == Every time Firefox opened == I'm not sure

Alle svar (3)

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

See http://kb.mozillazine.org/Firefox_hangs and Firefox hangs or is not responding - How to fix (Hang at exit)

AnonymousUser
AnonymousUser Spørgsmålsstiller
more options

My cpu does not hit 50%, maybe around 60,000k but most of the time it takes several minutes for Firefox to completely flush from the system after hitting 'exit'. This slows down the opening of other programs, and, if I say "Whoops, I need to get back into Firefox quickly - I forgot to do something!" and try to reopen it again, it tells me Firefox is still running and I have to wait until it has flushed completely.

Stan

AnonymousUser
AnonymousUser Spørgsmålsstiller
more options

Thanks cor-el. I think I found the problem. It was Comodo Anti-virus that was causing the problem as stated by the link you gave me. But Comodo seems to have updated and sorted that problem out completely now its totally fine.

Thanks again, Michael