nightly on x86 consumes a large amount of cpu

RESOLVED INCOMPLETE

Status

()

Core
General
--
major
RESOLVED INCOMPLETE
3 years ago
2 years ago

People

(Reporter: Jamie_, Unassigned)

Tracking

({perf})

40 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(firefox40 affected)

Details

Attachments

(1 attachment)

6.75 MB, application/octet-stream
Details
(Reporter)

Description

3 years ago
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

3 years ago
Status: NEW → UNCONFIRMED
Ever confirmed: false
(Reporter)

Comment 1

3 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)
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.
Component: General → General
Flags: needinfo?(gavin.sharp)
Product: Firefox → Core
(Reporter)

Comment 3

3 years ago
Created attachment 8601894 [details]
profile

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)
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

2 years ago
Jamie, did you get this sorted out?
Keywords: perf
Whiteboard: [closeme 2016-02-20]

Comment 6

2 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 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.