Closed Bug 1586488 Opened 6 years ago Closed 6 years ago

Each instance of FF uses up 15 - 20% CPU, wile no tasks are open and about:performance reports no to little load.

Categories

(Core :: Performance: General, defect)

69 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: walter.bishop, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

I updated my Arch install with FF going from 69.0.1 to 69.0.2 when I recognized that FF used up 20% CPU. I've an eye on my CPU as I'm using 6 of my 8 cores for BOINC workloads which stop when the overall load exceeds 20%.

Actual results:

I restarted the browser and the machine but there was still a load without any page open, just an empty tab. When I start my other profile, the second instance uses 15 - 20% also.

https://perfht.ml/33f6iRB

Expected results:

No CPU load without anything open.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Performance Monitoring
Product: Firefox → Toolkit

Just realized that the load isn't present when in safe mode. When about:performance isn't reporting anything, how to deduct which add-on is the culprit?

Your profiling results are not useful, they do not contain information about content/extension processes. Please run another profiling session and do not remove key information from the profiling results before generating a link to them.

Component: Performance Monitoring → Performance
Product: Toolkit → Core

Had to explicitly add those parts. I hope this contains the information you need. https://perfht.ml/2pOLz8D

When disabling the KeePassXC-Browser extension the load vanishes. I opened a bug report on their Github https://github.com/keepassxreboot/keepassxc-browser/issues/629

Sorry for the inconvenience. Please close the bug at your discretion.

Thanks for looking into the issue and filing the addon issue.
Closing this one.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.