Closed
Bug 927507
Opened 12 years ago
Closed 7 years ago
High CPU utilization
Categories
(Core :: XPCOM, defect)
Tracking
()
People
(Reporter: alice0775, Unassigned)
References
Details
(Keywords: regression, testcase)
Attachments
(1 file)
|
32.43 KB,
application/x-zip-compressed
|
Details |
This is spun off from Bug 927377
Steps To Reproduce:
1. Open http://frozenbyte.com/ (VG studio)
or Open testcase
Actual Results:
Firefox process (in process manager of Win 7) shows more 30% of CPU use.
Regression window:
Bad (around CPU 20%):
http://hg.mozilla.org/integration/mozilla-inbound/rev/89ad76a08a74
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20121211 Firefox/20.0 ID:20121211125858
More Bad (around CPU 30%):
http://hg.mozilla.org/integration/mozilla-inbound/rev/9602f98a6a70
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20121211 Firefox/20.0 ID:20121211143159
Pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=89ad76a08a74&tochange=9602f98a6a70
In local build:
Bad: 9dffd2d825c9
More bad: 513ec84b5c88
Regressed by: 513ec84b5c88 Vladimir Vukicevic — b=731974, requestAnimationFrame generates too short/long frames (incl. bug 799242); r=bz,smaug,roc,ehsan
Updated•12 years ago
|
Flags: needinfo?(vladimir)
I can reproduce it. It looks like it went from "bad" to "more bad", which really sounds more like we're just rendering more frames now than we were before. Not sure what the script is doing, but I'd guess it's the animation/slideshow thing at the top.
Flags: needinfo?(vladimir)
Comment 2•7 years ago
|
||
WFM (very modest CPU usage) with testcase and http://frozenbyte.com/ using nightly build from July on windows 7.
Alice, do you agree?
Flags: needinfo?(alice0775)
Keywords: testcase
| Reporter | ||
Comment 3•7 years ago
|
||
Fixed range:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=786737c759d7&tochange=fa25a75b4ad9
Fixed by: Bug 1060200
Status: NEW → RESOLVED
Closed: 7 years ago
Depends on: 1060200
Flags: needinfo?(alice0775)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•