Closed Bug 459477 Opened 17 years ago Closed 16 years ago

Firefox locking up CPU Usage to 100% during software update process and filling memory with 150MB

Categories

(Toolkit :: Application Update, defect)

Product:
Toolkit
Component:
Application Update
Version:
1.9.0 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: zoltan.grsic, Unassigned)

References

Details

(Keywords: hang)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 I noticed it this morning. Don't know is the problem persistent but while trying to go to any page Firefox locked the CPU usage to 100% and filled the memory with 150Mbytes of data. Have tried to check what could cause this and I saw that it was downloading the newest update today on Oct 11 2008. For now it stopped doing the cpu lock up but still concerned. Could someone look into this or this just happened with my system?! Thanks. Reproducible: Didn't try Steps to Reproduce: 1. Starting Firefox 2. Firefox downloading newest update 3. Firefox locking CPU to 100% during update Actual Results: For now the cpu usage is back to normal but still there is 150Mbytes of data in the memory under Firefox process... Expected Results: Not locking the CPU Usage to 100%...slowed the machine which is a relatively good P4
Keywords: hang
Version: unspecified → 3.0 Branch
Summary: Firefox locking up CPU Usage to 100% during software update process and filling memory with 150Mbyte's → Firefox locking up CPU Usage to 100% during software update process and filling memory with 150MB
Severity: minor → normal
Component: General → Application Update
Product: Firefox → Toolkit
QA Contact: general → application.update
Version: 3.0 Branch → 1.9.0 Branch
Reporter, Please update if you are able to still reproduce. If yes, please start Firefox in Safe Mode (http://support.mozilla.com/kb/Safe+Mode) to check if an extension is the cause of the mentioned issue.
Whiteboard: [closeme 2010-05-28]
No response to comment #2 - resolving -> incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2010-05-28]
You need to log in before you can comment on or make changes to this bug.