Firefox with NoScript is nearly unusable on a busy system (pages won't load if CPU is used heavily)
Categories
(Core :: Performance: General, defect)
Tracking
()
People
(Reporter: greg323464, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:144.0) Gecko/20100101 Firefox/144.0
Steps to reproduce:
While the computer is under heavy load (such as letting Adobe Lightroom import a set of files, where CPU usage may be 400-1000%), FireFox becomes unusable for navigating to new pages or reloading existing ones.
Actual results:
FireFox cannot load a new URL or reload an open page for extremely long periods of time. This can sometimes be several minutes (eventually if often loads a page even while a heavy load is ongoing).
Note there are numerous "FirefoxCP Isolated Web Content" threads active in MacOS Tahoe in this scenario. I am testing with 10+ browser tabs in both FireFox and other browsers. It does not matter if I try to reload 1 tab or multiple, even small requests will not proceed while the system is under load.
Expected results:
At the same time Firefox fails, Chrome and Brave are able to continue working as if there were no competing processes. There is no perceptible lag in other browsers at any time, while Firefox immediately under heavy load conditions.
Comment 1•5 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance: General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Tahoe (various versions have failed, currently using 26.1 Beta, 25B5072a)
Possibly, but the key thing I see with this bug is a failure to load or reload a page while the system is under heavy load. However, I can usually interact with a page just fine if it was loaded before things got busy in the background outside FireFox.
Comment 6•5 months ago
|
||
Did you see anything like this before upgrading to Tahoe?
I am not sure. I've seen the issue for a while, but started using Tahoe in June. I would not be surprised if Tahoe is a factor, but I wouldn't assume it is a trigger and don't have an easy way to test an older OS.
Comment 8•5 months ago
|
||
Hi Greg!
Could you test with the latest nightly and check if the problem still occurs for you?
Hi Bas-
I just tested with firefox-147.0a1.en-US.mac (while Lightroom was running heavy import/ convert operations in the background). Production Firefox (v145.0.1) stalls and is unable to load pages in any reasonable amount of time, but the Nightly seems to run normally.
Regards,
Greg
| Reporter | ||
Comment 10•4 months ago
|
||
Based on that success, I tried disabling extensions and it appears the root issue is NoScript (v13.4). When that is disabled, production FireFox loads quickly even with heavy background tasks. But when enabled, the problem returns.
Updated•4 months ago
|
Comment 11•4 months ago
|
||
The severity field is not set for this bug.
:bas.schouten, could you have a look please?
For more information, please visit BugBot documentation.
Comment 12•4 months ago
|
||
(In reply to Greg from comment #10)
Based on that success, I tried disabling extensions and it appears the root issue is NoScript (v13.4). When that is disabled, production FireFox loads quickly even with heavy background tasks. But when enabled, the problem returns.
Is everything working well for you now? My theory here is that this was a combination of a browser issue in older versions and the noscript extension.
| Reporter | ||
Comment 13•4 months ago
|
||
I am not immediately seeing an issue now while pushing LR to 800-1000% in the background. Currently running FireFox v145.0.2 (updated Nov 25) and NoScript v13.5 (updated Nov 29), so newer than when I failed 10 days ago. It appears it may be resolved.
Comment 14•4 months ago
|
||
The severity field is not set for this bug.
:bas.schouten, could you have a look please?
For more information, please visit BugBot documentation.
Comment 15•4 months ago
|
||
This was fixed with the OS X priority changes then.
Description
•