Closed
Bug 101943
Opened 23 years ago
Closed 23 years ago
javascript strict errors in consoleBindings.xml - browser hangs 99% CPU
Categories
(SeaMonkey :: UI Design, defect, P2)
SeaMonkey
UI Design
Tracking
(Not tracked)
mozilla0.9.7
People
(Reporter: coffeebreaks, Assigned: paulkchen)
Details
(Keywords: hang, perf, qawanted)
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4+) Gecko/20010923 BuildID: 2001092308 I was surging and on ChatZilla, and my browser started to hang (99% CPU) I had the following message. I've found something for the current 99% CPU problem. My Javascript console is filled up with messages like: "Error: this.console.appendItem is not a function Source file: chrome://global/content/consoleBindings.xml#console-box.init() Line 5" in around 2 seconds the scrollbar is minimized (as the text area is filled up very quickly)! I had to kill the browser (Ouch). The only line I found a reference to that function in that file is in line 59. observe : function(aObject) { this.console.appendItem(aObject); } Not tried to reproduce.
Reporter | ||
Comment 1•23 years ago
|
||
Several changes - Changing Component from 'Javascript Engine' to XPApp (as seen in bug 72455) - Changing title from "Javascript hangs - 99% CPU" to "javascript strict errors in - consoleBindings.xml - browser hangs 99% CPU" - making critical (as I had to kill and lost both browser, ChatZilla) - Putting platform and OS to all.
Severity: normal → critical
Component: Javascript Engine → XP Apps
OS: Windows 2000 → All
Hardware: PC → All
Summary: Javascript hangs - 99% CPU → javascript strict errors in consoleBindings.xml - browser hangs 99% CPU
Comment 2•23 years ago
|
||
Setting default owner and QA -
Assignee: rogerl → pchen
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: pschwartau → sairuh
Reporter | ||
Comment 3•23 years ago
|
||
I'm the reporter and I have a question that is unrelated to that bug in particular, but related to bugs like this one. I end up often with Mozilla taking 99% CPU. Usually I do not report them because I do not find their origin and can't reproduce them. Are there any methods for retrieving some information about the actual state of the program so that I can report a bug with some information? The problem is that I am on W2k and don't know a lot the commands... Perhaps using some of Visual C++ Tools? Should I use Talkback and generate a report? Are there any help on the Mozilla Web site saying how to help you investigate those bugs?
Comment 4•23 years ago
|
||
actually, talkback only generates a report when the app crashes, not when it hangs. :(
Severity: critical → major
Priority: -- → P2
Target Milestone: --- → mozilla0.9.7
Comment 6•23 years ago
|
||
*** This bug has been marked as a duplicate of 85831 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment 7•23 years ago
|
||
mass verification of duplicate bugs: to find all bugspam pertaining to this, set your search string to "DuplicateBugsBelongInZahadum". if you think this particular bug is *not* a duplicate, please provide a compelling reason, as well as check a recent *trunk* build (on the appropriate platform[s]), before reopening.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•