Firefox Community Forum

Why does Mozilla 154.0 always stall after a couple of minutes? It is a hell of a mess. I couldn't place this question without resorting to an older version of Firefox :-[[

Did anybody test V 154.0 anytime, at all?

I unfortunately updated a Windows 10 computer to this version of Firefox.

As such, I cannot provide you with troubleshooting information, because the new browser 154.0 does not work. At. All.

I did all the usual stuff like restarting the computer, the users of Windows OS junk are used to anyway. The Task Manager shows not less than 16 Firefox-processes, with a truckload of memory usage, having opened just one browser tab. Waiting for 20 minutes for firefox to show me the grace of continuing its operation didn't help either.

Any ideas?

When trying to do a search for a video in YouTube Studio, the search seems to freeze. Doing a similar search in Microsoft Edge works OK. This problem started happening several months ago. I've tried clearing the cache for YouTube pages.

Firefox has been running incredibly slow. I currently only have this window open, but if I open my task manger it shows 10 Firefox windows running. If I right click and end task, it will end the task, but shortly there after a new one will pop up. 1 of the is running in efficiency mode. I assume this is what is slowing down performance, but I do not know how to fix.

I have removed Firefox and installed fresh the latest version 137.0.1 to address the issue of not being able to start a new tab or a new window. I am writing this from the initial window that opens when Firefox is launched. If I try to open a new tab it will hang with the blue circle displaying. If I click anywhere on the window if will grey out the background and display the error message :

Firefox is not responding

if you close the program, you might lose information

-> Close the program -> Wait for the program to respond

Tried waiting and it never comes back. Only option is to close the program. After that there is a message that is reporting the issue to Microsoft.