Closed Bug 1877482 Opened 2 years ago Closed 1 year ago

Just updated to Firefox v122.0 and my Unifi controller page CPU usage has shot up 10x

Categories

(Core :: Widget: Gtk, defect)

Firefox 122
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: dashthechi, Unassigned)

Details

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

Steps to reproduce:

Firefox desktop did it's usual automatic update in the background and wanted me to restart. This is normal action.

Actual results:

When I did, my Unifi Network Controller page, which is java based I believe, CPU usage went from 0.5% to 5%. Doesn't seem like much but a 10x increase in usage is concerning. If I click on another tab to view another webpage, the usage drops back to 0.5% or less. Usage only increases when the controller page is being viewed.

Expected results:

No change in CPU usage was expected. I've been using Firefox for a long time and didn't see this happen as Firefox upgraded. I removed Firefox and installed v115 esr channel for the security updates but not as new features, and the usage dropped back to normal. Something changed in v122. No other software was updated or changed in that one hour period when the update occurred.

Running Ubuntu 22.04.03 LTS on Intel i9-9900k with 32gigs of ram.

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

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Can you use mozregression tool to find broken commit?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool
Thanks.

Flags: needinfo?(dashthechi)

A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Given that the bug is still UNCONFIRMED, closing the bug as incomplete.

For more information, please visit BugBot documentation.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(dashthechi)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.