Closed
Bug 1160810
Opened 9 years ago
Closed 8 years ago
nightly on x86 consumes a large amount of cpu
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
firefox40 | --- | affected |
People
(Reporter: Jamie_, Unassigned)
Details
(Keywords: perf)
Attachments
(1 file)
6.75 MB,
application/octet-stream
|
Details |
while running on linux x86 the nightly will consume large amounts of wpu with little to no reason. while starting nightly cpu consumption on a i5 quad core jumps from 4 to 40 percent and when on a open window with just a blank tab (this is a decent amount of an i5 quad), it doesn't idle it it varies from 4 all the way up to 20 with no activity.
Reporter | ||
Updated•9 years ago
|
Status: NEW → UNCONFIRMED
Ever confirmed: false
Reporter | ||
Comment 1•9 years ago
|
||
Can you take a look at this, i was not sure where to put it or who to ni on it so i did you since you are more in the firefox browser field than i am.
Flags: needinfo?(gavin.sharp)
Comment 2•9 years ago
|
||
Without more info or a reproducible test case, it will be hard to chase this down. https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler is another possible tool for finding Firefox CPU usage causes.
Flags: needinfo?(gavin.sharp)
Product: Firefox → Core
Reporter | ||
Comment 3•9 years ago
|
||
Im not sure how much this helps gavin, but this was the profile idling with just Cleopatra open then clicking the restart firefox button on the profiler.
Flags: needinfo?(gavin.sharp)
Comment 4•9 years ago
|
||
I'm sorry, but I don't have the time to dive into this right now. You could try posting to dev.platform or seeing if someone in #developers can help you debug it.
Flags: needinfo?(gavin.sharp)
Comment 5•8 years ago
|
||
Jamie, did you get this sorted out?
Keywords: perf
Whiteboard: [closeme 2016-02-20]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2016-02-20]
You need to log in
before you can comment on or make changes to this bug.
Description
•