Closed
Bug 447910
Opened 18 years ago
Closed 17 years ago
Firefox processes takes 100% CPU (on one core) after closing all browser windows
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: alexthegamer, Unassigned)
Details
(Whiteboard: closeme 2009-05-25)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
After using Firefox 3.0.1 (issue also exists in Firefox 3.0) on Windows Vista Home Premium (32-bit), and closing the browser (all frames), the firefox.exe processes will remain and use 100% of one CPU core. (Definitely affects dual-core systems, may affect solo-core)
Reproducible: Sometimes
Steps to Reproduce:
1. Launch Firefox 3.0.1 on Windows Vista Home Premium
2. Browse web sites (prolonged period of time with various sites seems to increase this)
3. Close Firefox
4. Attempt to open Firefox again, and see a dialog indicating that Firefox is already running
5. Open Task Manager and find firefox.exe using 100% of one core.
Actual Results:
Firefox processes (firefox.exe) keeps running, (stuck in an infinite loop?) and requires a force quit (end process) to be able to use Firefox again.
Expected Results:
Firefox closes and opens properly every time.
HP tx2000z Laptop with AMD TL-62 (2.1GHz/core, 2 core) laptop, running 32-bit Windows Vista Home Premium.
Plug-ins installed:
Adobe Flash
Adobe Shockwave
Adobe Acrobat
Sun Java
Microsoft Windows Media Player
Comment 1•17 years ago
|
||
Alex
Do you get the same results with the latest beta of 3.5?
available from http://www.mozilla.com/en-US/firefox/all-beta.html
If you don't see the problem then this may have been fixed by the closed bugs that are blocking bug 453178.
If you do see this, then the blockers to bug 407981 should be checked. and see bug 453178 comment 1.
Whiteboard: closeme 2009-05-25
Version: unspecified → 3.0 Branch
Comment 2•17 years ago
|
||
Please reopen this bug if it appears with a recent version of firefox in a new profile.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•