Firefox constantly freezes
Categories
(Core :: Performance: General, defect)
Tracking
()
| Performance Impact | pending-needinfo |
People
(Reporter: bluedzins, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:137.0) Gecko/20100101 Firefox/137.0
Steps to reproduce:
For now this report looks vague I know, but simply I don't have concrete steps to reproduce this issue.
Previously I used I believe version 102 for quite some years and I didn't have such issue once (!). Then I was forced to upgrade FF (because expiring certificates), initially it was 136 and now 137, both have this issue.
My workflow is as follows:
- I run several instances of FF, with multiple tabs in each -- those are "permanent" instances, online dictionaries, weather forecast, puzzle solver, AI sites, etc.
- every day I run more FF instances with temporary tasks, like watching YT videos, StackOverflow, online stores, more or less I remember to close them after some time. For sure it is not the case I run 10000 of pages at the same time, and I didn't change my habits compared to 102 time. It could be I have 2 pages more, but not 10 times more
More or less, every week I have at least one freeze all of the sudden. Firefox simply becomes totally unresponsive and I have to kill it (all instances). It looks the current page (the one I observe freeze on) is irrelevant, it could be even my own, local, page.
I run openSUSE 15.3, exactly the same setup as before, I just upgraded FF, nothing else.
|
||
Comment 1•1 month ago
|
||
Unfortunately this is not really actionable at the moment.
Please try recording and sharing a performance profile:
- Go to http://profiler.firefox.com/
- Start recording and repeat the action
- Upload the profile and share the link here
(In reply to Francesco Lodolo [:flod] from comment #1)
Unfortunately this is not really actionable at the moment.
Yep, I wish I have at least some meaningful steps.
- Start recording and repeat the action
By "action" do you mean some random thing, or should I keep recording for a week, and upload after the freeze?
- Upload the profile and share the link here
If the former, the link is: https://share.firefox.dev/3RqMllK
|
|
||
Comment 3•1 month ago
|
||
You should start recording when you see Firefox freezing (assuming it will start).
This is not possible, because FF is frozen. It happened few seconds ago, so to clarify. Frozen program does not refresh, does not display actively its UI. So let's say I have two programs running, like Rider and Firefox. When FF is frozen when I switch to Rider I see Rider of course, when I switch to FF I see... Rider. I.e. it is not Rider technically speaking, but since FF does not show anything it looks (visually) as Rider, but it is window of Firefox really.
The only operation I can do is not with Firefox, but on Firefox -- killing it. But this kill comes from desktop, not from FF itself.
|
|
||
Comment 5•1 month ago
|
||
Not exactly sure how this can be debugged. Trying to move to Performances to see if folks have an idea.
Some facts. As this report goes, there were 3 freezes -- before opening this report, then 2025-04-21, and today (2025-05-02).
And today looked different than any before.
- I tried to open/run new instance (window)
- nothing happened
- as it turned out, FF froze, I could not interact, but the page image was not lost, i.e. when I switch back and forth between windows, the relevant data was shown correctly
- I decided to kill FF
- the moment I did it, the new window/instance show up (by itself) greeting me with info I have new upgraded FF
- I close it and run FF afresh
- since this greeting was the last FF session, I could not restore the killed one
I am not sure if this means, there is a hint/indication the freezing is caused by FF upgrades (I don't know if there were any previously), or this is just a separate issue, but simply manifesting the same way by freezing.
|
||
Comment 7•14 days 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 8•11 days ago
|
||
Hrm, one noticeable thing in that profile is that there's a 250ms window where Firefox doesn't get scheduled and it cause quite a jank there. It's nothing quite as severe as you're describing, but do you often see shorter periods of unresponsiveness like that?
This type of short freeze suggests severe background activity or something like that.
But I'm not sure it's the same issue as you're describing.
Also ni?jld to see if this sounds at all familiar and could be related to updates and the forkserver.
In context of being responsive, it human terms (what my eye sees and what I feel) I would say Firefox is responsive for me (except for this issue). What is surprising for me, so far there was no more freezes. So the frequency of freezes is lower than in period between this jump-upgrade (from around v.102) to posting this report.
Description
•