Closed
Bug 606711
Opened 15 years ago
Closed 15 years ago
Firefox freezes with 100% cpu load when selecting no page style for Add-ons Manager
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | final+ |
People
(Reporter: whimboo, Unassigned)
Details
(Keywords: hang, regression)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b8pre) Gecko/20101023 Firefox/4.0b8pre
This seems to be a recent regression. Haven't seen this a while back when checking this particular steps. As what I can see with the latest nightly build and some extensions installed, switching the page style to no style for the add-ons manager completely freezes Firefox. Also the process takes up to 100% cpu load. In a fresh profile without any extensions installed the style is switched after a couple of seconds but as more as extensions you have installed, as longer it takes.
Steps:
1. Create a fresh profile and install a couple of extenions
2. Open the add-ons manager
3. Select "View | Page Style | No Style"
After step 3 Firefox will freeze and consume 100% cpu load for a long time. I killed the process after about minutes, so I can't tell if we ever switch the style.
| Reporter | ||
Updated•15 years ago
|
blocking2.0: --- → ?
| Reporter | ||
Comment 1•15 years ago
|
||
Regressed between the builds 10091303 and 10091403.
PASS: http://hg.mozilla.org/mozilla-central/rev/84ee6bc0484d
FAIL: http://hg.mozilla.org/mozilla-central/rev/5588c9796f0b
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=84ee6bc0484d&tochange=5588c9796f0b
Not sure which check-in could have been caused this.
Keywords: regressionwindow-wanted
Comment 2•15 years ago
|
||
This no longer happens for me, can you confirm?
| Reporter | ||
Comment 3•15 years ago
|
||
Yeah, this has been fixed by another patch, but I can't exactly remember which one. Lets mark it as WFM.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Updated•15 years ago
|
blocking2.0: ? → final+
You need to log in
before you can comment on or make changes to this bug.
Description
•