Closed
Bug 425862
Opened 17 years ago
Closed 17 years ago
100% CPU usage, CSS issue with list-style-position
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: alice0775, Unassigned)
References
()
Details
Attachments
(1 file)
586 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.8.1.13) Gecko/20080313 Firefox/2.0.0.13 (ayakawa SSE2-PGU) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-us; rv:1.9pre) Gecko/2008032805 Minefield/3.0pre When I visit http://firefox.geckodev.org/index.php?userChrome.js, CPU usege is 100%. Reproducible: Always Steps to Reproduce: 1.go to http://firefox.geckodev.org/index.php?userChrome.js 2.CPU usege is 100%. 3. Actual Results: CPU 100% forever. Expected Results: After load the page, CPU will settle. The above page use following css. ul,ol{ list-style-position: inside; margin: 15px;} If I apply following userContent.css to the page, CPU will settle. ul,ol{ list-style-position: outside !important; margin: 15px;}
Reporter | ||
Updated•17 years ago
|
Version: unspecified → Trunk
Comment 1•17 years ago
|
||
I can confirm this Mozilla/5.0 (Windows; U; Windows NT 6.0; rv:1.9b5pre) Gecko/2008032601 SeaMonkey/2.0a1pre. The URl takes 50% CPU on my dualcore system
Status: UNCONFIRMED → NEW
Component: General → Layout
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → layout
Reporter | ||
Comment 2•17 years ago
|
||
Regression window is: 2008-02-18-04-trunk --- CPU will settle. 2008-02-19-04-trunk --- 100% CPU usage.
Comment 3•17 years ago
|
||
Maybe the checkin of bug 401291 is concerned?
Reporter | ||
Comment 4•17 years ago
|
||
As for this problem, the scroll of the page becomes extremely slow not only the rate of use of the CPU becomes 100%. This problem is not yet settled. In addition, there does not seem to be an action for the solution. This problem did not happen in Firefox2.0. I cannot specify the check-in that caused this problem, but think that there is a problem in the review system which was not able to see through this problem.
Reporter | ||
Comment 5•17 years ago
|
||
I think that this issue was solved by checked in Bug 436453.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Depends on: 436453
You need to log in
before you can comment on or make changes to this bug.
Description
•