Closed Bug 296975 Opened 20 years ago Closed 20 years ago

High CPU load, error repeated forever on command line

Categories

(Thunderbird :: General, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmccabe, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050607 Firefox/1.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050607 Firefox/1.0+

20050607 build, around 10:00 hours Pacific time. Launch of TBird uses huge
amount of CPU while reporting this error to the command line:

*** Checker.onError: error during load
*** update url: chrome://mozapps/locale/update/update.properties
*** Checker.findUpdates: sending request to
chrome://mozapps/locale/update/update.properties
*** Checker.onError: error during load
*** update url: chrome://mozapps/locale/update/update.properties
*** Checker.findUpdates: sending request to
chrome://mozapps/locale/update/update.properties
*** Checker.onError: error during load
*** update url: chrome://mozapps/locale/update/update.properties
*** Checker.findUpdates: sending request to
chrome://mozapps/locale/update/update.properties

TBird is usable while this happens, but is doing great damage to the rest of the
system due to 100% CPU use.

Reproducible: Always

Steps to Reproduce:
1. Launch TBird from shell
2. Watch in horror as CPU spikes and errors are repeated over and over
Behavior is gone. I suspect Ben Goodger's checkin:

2005-06-07 17:21	ben%bengoodger.com 	mozilla/ toolkit/ mozapps/ update/ public/
nsIUpdateService.idl 	1.17 	13/0  	Implement new timer manager for handling of
update interval timers for the update service and the extension manager
2005-06-07 17:21	ben%bengoodger.com 	mozilla/ toolkit/ mozapps/ update/ content/
updates.js 	1.6 	3/4 
2005-06-07 17:21	ben%bengoodger.com 	mozilla/ toolkit/ mozapps/ update/ src/
nsUpdateService.js.in 	1.18 	76/20 

fixed it.
Severity: normal → major
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.