Firefox Community Forum

The problem of hanging on specific web pages but not always in the same place greatly increased 11/22/2026 running Firefox 115.38ESR under Windows 7 so I suspect that it is due to some widespread update and a new esr update is needed. 115.43.1esr did not help. Sometimes it happens while loading a page, sometimes when attempting to scroll the page and sometimes when entering data into a field.

I've used Firefox for years and am embarrassed to submit this question via Chrome. Lately, almost invariably after updating, Firefox shows "not responding" if you click anywhere in the window. Eventually, maybe after half an hour, it does respond, and everything works like it always did. If this is normal behavior for Firefox, so be it, but it seems peculiar to me. Advice?

My browser is using 2,3 Gb of extra ram it goes away by restarting but comes back in 5-10 min. It occurs wathing twich, i have tried disabling extentsions but it doesn't work. in about:memory the readout is as thoug it is keaping an extra copy of open browser files in ram.

2,511.83 MB (100.0%) -- heap ├──2,301.00 MB (91.61%) -- committed │ ├──2,016.65 MB (80.29%) ── unused-pages/dirty │ ├────230.75 MB (09.19%) ── allocated │ ├─────32.96 MB (01.31%) ++ bin-unused │ └─────20.65 MB (00.82%) ++ (2 tiny) └────210.82 MB (08.39%) -- decommitted

    ├──210.21 MB (08.37%) ── unmapped
    └────0.61 MB (00.02%) ++ unused-pages

I have turned on compact mode, so i have to hover to the left side to access it. I usually go to the left side, it appears and i do what i wanna do. But today, when i go to the left side it appears as usual but automatically disappears again without me doing anything. Also if i click on something on the toolbar it does not register but it clicks on whatever website that is underneath it. It doesn't happen all time though, sometimes its working like before. I don't know how to find the exact cause.

When I use incognito mode and open and close multiple incognito tabs, closing the tabs and closing the last incognito mode browser instance leaves behind what appears to be Firefox processes for each closed tab. When I return to my open normal mode tabs, I cannot browse from the normal tabs, I get spinning circles and no progress. The only way to clear this is to close the normal browser and all its tabs, then use the task manager to manually end the remaining Firefox (zombie) tasks that seem to be left behind by the incognito tabs that were already closed. Then when I restart Firefox and restore my previous session, I can browse normally again.

It seems like there may be a bug here that the incognito tabs are not properly ending their processes when the tabs close. I have no involvement in the innards of Firefox, and simply wanted to report my difficult experiences to help in identifying problems. I am using Windows 11 and the latest version of Firefox - 158.0. I have seen this problem for at least a month or so. That means at least a few earlier versions of Firefox shared this issue.

I typically keep more than 10 tabs open in normal mode, and for incognito mode, I usually progress through at least ten more tabs, with two or three open at a time, but closing them after a few minutes as I complete each task. When I complete the browser tasks in incognito mode I make sure all the incognito tabs are closed. When I return to an open tab in normal mode and click on a link to browse onward, I never see any progress. I close the Firefox browser and all the normal tabs. I open the Windows task manager and even though I just closed Firefox, I see between 10 and 12 Firefox processes. I use the "end process" command in task manager to manually close what I think of as zombie Firefox processes. When I then open a new instance of Firefox, and use the History section to restore my previous session, all my normal mode tabs reopen, and I can use links in those tabs normally to proceed with browsing normally.

I am not familiar with the Firefox community and have not participated in your forums. I hope this might help you identify and fix any bug that may be present. I feel like I have a work around that is only slightly awkward.