Closed Bug 1835317 Opened 2 years ago Closed 2 years ago

Increased CPU load with 113.0.X

Categories

(Core :: Performance: General, defect)

Firefox 113
defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: bugs, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/112.0

Steps to reproduce:

I'm a tab hoarder and have tons of tabs open for various topics, about 40 windows with a total of about 440 tabs are open and about 10 extension installed.
Firefox is running on MacOS 13.3.1 with Microsoft Defender (lightly managed device).
Memory usage by Firefox is about 9GB, the Firefox internal task manager says most of load is coming from Firefox itself (but it might be an aggregation of all the open tabs, idk for sure).
(I'd be hapy to provide any profiling information.)

Actual results:

When upgrading from Firefox 112 to 113 I see an increased CPU load with the very same profile. I went through 113.0, 113.0.1 and 113.0.2 and didn't see an improvement.
(Increased load means dramatically more fan noise and being barely able to do anything else on this notebook.)
Downgrading to 112 reduces load again.

Expected results:

Firefox should not increase CPU load on the very same profile / amount of windows/tabs/extension when upgrading.

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Product: Firefox → WebExtensions
Component: Untriaged → Performance
Product: WebExtensions → Core

This bug was moved into the Performance component.

:bugs, could you make sure the following information is on this bug?

  • For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
  • For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
  • Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.

If the requested information is already in the bug, please confirm it is recent.

Thank you.

Flags: needinfo?(bugs)

With no answer from the reporter, we don’t have enough data to reproduce and/or fix this issue. Please reopen or file a new bug with more information if you see it again. Details of our performance triage process can be found at https://wiki.mozilla.org/Performance/Triage.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INACTIVE

Sorry for delay, somehow the messages must have been filtered away and I don't login into https://bugzilla.mozilla.org/ on a regular basis.
Nonetheless the issue was could be resolved by clearing cache. It's something which happens from time to time, especially after upgrades (or so it seems).

Meanwhile I even have a script for that:

#!/bin/sh

PROFILE_NAME=...

FF_PROFILE_BASE_DIR=~/Library/Application\ Support/Firefox/Profiles
FF_PROFILE_DIR=${FF_PROFILE_BASE_DIR}/${PROFILE_NAME}

rm -rf "${FF_PROFILE_DIR}/storage/to-be-removed/*"
rm -rf "~/Library/Caches/Firefox/Profiles/${PROFILE_NAME}/cache2/*"
You need to log in before you can comment on or make changes to this bug.