Closed
Bug 282406
Opened 20 years ago
Closed 20 years ago
CPU pegged at >95% usage on some pages (NS_ERROR_FAILURE)
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: drewlite, Assigned: mikepinkerton)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O) Gecko/20040906 Camino/0.8+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O) Gecko/20040906 Camino/0.8+ On some pages (http://www.arstechnica.com) the CPU will get pegged at >95% and during this, the console will output this repeatedly: 2005-02-15 15:55:35.606 Camino[575] JS error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMScreen.width]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://a.as-us.falkag.net/dat/dlv/aslmain.js :: uC :: line 18" data: no] I have to restart Camino to solve the problem. on quit I get this: HISTORY DEBUG: Commit() in CloseDB() returned err 0x00000000 HISTORY DEBUG: historyFile exists: 1 HISTORY DEBUG: OpenExistingFile(/Users/drew/Library/Application Support/Camino/history.dat) HISTORY DEBUG: OpenOldFile returned err 0x00000000 (file 0x2ebaa38) HISTORY DEBUG: CanOpenFilePort returned err 0x00000000 (canopen 1) HISTORY DEBUG: OpenFileStore returned err 0x00000000 (thumb 0x2e294c8) HISTORY DEBUG: DoMore or ThumbToOpenStore returned err 0x00000000 HISTORY DEBUG: CreateTokens returned err 0x00000000 HISTORY DEBUG: GetMetaRow return err 0x00000000 It seems that there are so many JS errors, that the system starts to lag trying to output them all. Reproducible: Sometimes Steps to Reproduce: 1.go to http://www.arstechnica.com 2. 3. Actual Results: CPU pegged at >95% usage stream of JS errors on console log
I noticed that there are similar bugs in the mozilla suite -- a search for NS_ERROR_FAILURE will return a similar bug for Windows: https://bugzilla.mozilla.org/show_bug.cgi?id=124354
wfm.
Mac OS X 10.3.8
2005021910 (v0.8+)
>User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O)
Gecko/20040906 Camino/0.8+
This build is too old.
Since the original bug report, I've tried newer builds (2005021708 (v0.8+)), and the problem seems to have gone away.
(In reply to comment #2) > >User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O) > Gecko/20040906 Camino/0.8+ > This build is too old. The original poster's build can't be Gecko/20040906 Camino/0.8+ if he's getting the History debug stuff in the console; smfr just added that ca. 20050203. drewlite@yahoo.ca, did you set a custom user-agent string at one time, using Camino Extra Prefs or by manually editing your user.js? If so, you might want to remove that line from user.js so Camino will always report the current build-date. However, closing as WFM based on comment 3 and comment 2; if this reappears in subsequent builds, you can reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•