1622317 - Enormous cooling fan speed when firefox is launched

Status: RESOLVED INCOMPLETE

(Core :: Performance: General, enhancement, P3)

Description

[ill-kas]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36

Steps to reproduce:

Launch firefox

Actual results:

Laptop cooling fan begins to work at enormous RPM when firefox is launched and this high RPMs are kept until firefox is closed. Completely removed and reinstalled, new blank installation of firefox causes the same issue. No such problem with other browser

Expected results:

Work at normal (low) RPMs

Comment 1

[Andrei Purice]

I cannot reproduce this issue on any of the versions 76.0a1 (2020-03-17) (64-bit), the release 74.0 or the beta one 75.0b5 on 3 different setups and they are working fine.

Be advised that downloading huge files or having multiple tabs opened are adding to the issue.

Do you experience any crash or unresponsiveness while using Firefox ? Is the laptop an old device?

Comment 2

[ill-kas]

The issue occures without downloading huge files or having multiple tabs opened. It is present even in newely installed blank mozilla with no tabs opened, no apps installed.
I did not xperience any crash or unresponsiveness while using Firefox. The laptop is 2 years old Lenovo IdeaPad 510-15ISK

Comment 3

[Michel Le Bihan]

Could you please open Task Manager (you can use the ctrl + shift + escape keyboard shortcut) and check if the cause is high CPU usage and check which process is using a big amount of CPU %?

Comment 4

[ill-kas]

On average nothing has high CPU usage, usually it is within 0-12%. Firefox in particular has 0-3 %, sometimes rises higher for a very short period of time but it is empty even at those moment (no tabs opened, no downloads).

Comment 5

[Michel Le Bihan]

Do you have antivirus software or some sort of software for optimizing performance running? Please disable it temporarily and check if you still experience this issue.

Comment 6

[ill-kas]

I have CCleaner, Clean Master and NOD Eset. Disabled all 3, the problem is still present.

Comment 7

[Andrei Purice]

Hey Kas,

You could try this "gfx.webrender.force-disabled = true" in about:config and see if it helps.
And this : about:preferences#general > Performance > Use recommended settings > Use hardware acceleration when available

Comment 8

[ill-kas]

Hi

Tried both, but unfortunately the situation is still the same

Comment 9

[Andrei Purice]

I want to try something else if you will agree. Can you perform a virus scan to check if there's no malware present?

Comment 10

[ill-kas]

I've performed a virus scan to check with ESET InternetSecurity. No malware or other issues detected.

Comment 11

[Andrei Purice]

Setting a component for this issue in order to get the dev team involved.
If you feel it's an incorrect one please feel free to change it to a more appropriate one.

Comment 12

[Mike Conley (:mconley) (:⚙️)]

Hi ill-kas,

Fans spinning up is generally a reaction to a temperature increase in the machine caused by increased activity - generally by the CPU or the GPU, but sometimes by other components.

If you're still able to reproduce this, I'd be interested in knowing what processes other than Firefox are consuming CPU / GPU and power during the time when the fans are spinning. If you launch Firefox, wait for the fans to spin, and then look in Task Manager, and sort by CPU usage, what's at the top? How about GPU usage? Power usage?

Are you also able to reproduce this if you launch Firefox in "safe mode" (go to Help > Restart with Add-ons Disabled).

Comment 13

[Kim Moir [:kmoir] ET]

Could you also capture a performance profile the next time you see this? https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem

Comment 14

[BugBot [:suhaib / :marco]]

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.