Very high cpu usage - 40% at idle even after reset

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
3 years ago
a year ago

People

(Reporter: dmaurand, Unassigned)

Tracking

40 Branch
x86_64
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150826023504

Steps to reproduce:

Full reset


Actual results:

Nothing


Expected results:

CPU usage should have dropped to what other browsers are using (approx 1 or 2% when idele)
(Reporter)

Comment 1

3 years ago
Created attachment 8654817 [details]
screenshot of mac activity monitor.

one FF tab open (a story on Salon.com). Chrome the window in focus.

Comment 2

3 years ago
Did you test with HWA disabled?
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Comment 3

3 years ago
Sorry, wrong link:
https://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration
Flags: needinfo?(dmaurand)
(Reporter)

Comment 4

3 years ago
turning off HWA definitely helped, and ABP on earlier had a strong effect. Now at approx 15% cpu consumption. [i will look for a way to attach a new screenshot.]

the attached is with FF in focus and one tab open.
(Reporter)

Comment 5

3 years ago
Created attachment 8655120 [details]
Revised screenshot - HWA off, ABP on
Flags: needinfo?(dmaurand)
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
Summary: Very high cpu usage - 40% at idle even after reset (v40.0.3 on Mac) → Very high cpu usage - 40% at idle even after reset

Comment 6

3 years ago
User Agent 	Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID 	20160126030244

Hi David, 

Are you experiencing the issue on the latest Firefox releases (Firefox 43 / Nightly 47)? I could not reproduce this on Firefox 43 and Nightly 47.
Flags: needinfo?(dmaurand)

Comment 7

3 years ago
Closing as incomplete due to lack of response from the reporter. Fell free to reopen the bug if you can reproduce the issue on a current build.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(dmaurand)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.