Closed
Bug 422374
Opened 17 years ago
Closed 15 years ago
Opening "Gmail settings" causes 100% CPU usage
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mkhaos7, Unassigned)
Details
(Whiteboard: [CLOSEME 2010-07-30])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
When trying to open the settings for Gmail it never ends loading and the cpu usage goes to 100%. I can still browse and even open other pages on gmail to see my e-mail, but 100% keeps at 100%.
Using the "new" Gmail version, with lables coloring and all other whistles.
Probably this is a JavaScript bug, but since i'm no JS expert, and don't even know where to start debugging i'm passing this one to the pros! :)
Reproducible: Always
Steps to Reproduce:
1.Login in a gmail account
2.Click on the settings button
Actual Results:
Settings page never shows up. "Loading" message is displayed on top of screen forever. Cpu usage goes 100%.
Expected Results:
Open the settings page and leave my CPU alone :)
Comment 1•17 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008031122 Minefield/3.0b5pre
This WFM; I see no significant change in CPU usage and certainly no hang.
Comment 2•15 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 3.0 Branch
Comment 3•15 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•