Closed
Bug 355247
Opened 19 years ago
Closed 19 years ago
Uses 100% CPU when running under a different user than the one who logged in into the GUI session
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 357852
People
(Reporter: awuest, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
If Firefox is run under a different user than the one who logged in, it uses 100% CPU and only browser windows can be opened, but no other windows like the error console or the about dialog.
This worked flawlessly with the 1.8.0 branch.
Reproducible: Always
Steps to Reproduce:
1. Log into the desktop
2. Open a terminal and su to a different user
3. Run Firefox from this terminal
Actual Results:
Firefox uses 100% CPU, and no windows except new browser windows can be opened.
Expected Results:
Normal CPU usage, and windows can get opened normally.
Reporter | ||
Comment 1•19 years ago
|
||
ktrace seems to indicate that Firefox is reading from the same two or three positions in classic.jar and en-US.jar over and over again, without end.
Reporter | ||
Comment 2•19 years ago
|
||
This behaviour occurs on 1.8.1 (tested with Firefox 2.0 RC1 and several older nightlies) and on trunk.
It works correctly with Firefox 1.5.0.x.
Reporter | ||
Comment 3•19 years ago
|
||
This is actually caused by setting nglayout.debug.disable_xul_cache to true. I was mistaken by the fact that only my not-logged-in user runs with this setup.
*** This bug has been marked as a duplicate of 357852 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•