Closed Bug 397252 Opened 18 years ago Closed 16 years ago

CPU 100% when carry out an any action

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Modex, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9a9pre) Gecko/2007092305 Minefield/3.0a9pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9a9pre) Gecko/2007092305 Minefield/3.0a9pre When opening menus, restore closed tab or open new CPU loading up to 100% Reproducible: Always Steps to Reproduce: 1. Restore closed tab 2. Open error console 3. See errors in it Actual Results: Errors in console and CPU loading 100% disturb for normal work in Firefox. Expected Results: No errors. There are 3 errors: 1) Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: XStringBundle :: getString :: line 17" data: no] Source: XStringBundle String: 17 2) Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: XStringBundle :: getString :: line 17" data: no] 3) Error: too much recursion Source: XPCSafeJSObjectWrapper.cpp String 434, symbol 49 Source code: if (arguments.length == 1) return this[arguments[0]];return this[arguments[0]] = arguments[1];
Could you give steps to reproduce that always show the bug, also without any add-ons installed and with a new profile? I also experience hangs in Minefield in the last few months but I can't reproduce them consistently.
Reporter, can you still reproduce the problem using the latest Firefox version? If not, can you resolve this bug as WORKSFORME?
Resolving as WORKSFORME. If this issue can be reproduce on Firefox 3.5, we will reopen the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.