Closed Bug 965695 Opened 10 years ago Closed 10 years ago

full cpu after exit

Categories

(Firefox :: General, defect)

26 Branch
x86
Linux
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jiang.qian, Unassigned)

References

Details

I exit firefox either by ctrl-w to close the last window, or by going to the menu and hit "quit". The window disappear but the process go on consuming 100% cpu. I can observe this by doing "top" under commandline. 100% cpu consumption persist until I kill it by issuing "killall firefox".

This behavior does not occur in firefox 25.1. It only appear in 26.
Version: 27 Branch → 26 Branch
I'm having a similar issue, and it seems to be related to the large amount of bookmarks I have. FWIW, the bug report for that issue is here: https://bugzilla.mozilla.org/show_bug.cgi?id=951934
I don't have a lot of bookmarks. <30. I believe I have found the website that's causing this. Amazingly it is gmail.

I open a gmail window, with html5 standard email view, from a profile that has no extension whatsoever. And I close the window. Firefox is then consuming 100% CPU.

This problem persists in 27.

I'm opening another bug report!
Flags: needinfo?
There is no need to open another report since you already opened this. It will just get marked as a duplicate (since that's what it would be).

I can't reproduce this issue on Ubuntu 13.04 32bit. What Linux are you using?
Flags: needinfo?(jiang.qian)
Flags: needinfo?
I'm using Ubuntu 10.04 32 bit, unfortunately. Mu old computer is too slow to run "fancy" unity. I disabled all the extensions and plugins in the firefox, and have a clean install of firefox 27 downloaded directly from the mozilla website. Nothing other than untar and run it. And the behavior happen in both full gmail and basic html site. Right now I'm running firefox 24esr which does not it.
Flags: needinfo?(jiang.qian)
Somehow the bug is fixed in firefox 28.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.