All Products Support Forum

Firefox just stops responding when trying to load a web page. The only way to get it back working is to reboot the computer. I have tried quitting the application but when I try to restart it it doesn't respond and I end up having to force quit and reboot the computer and then it will work fine. MacBook Pro (15" 2017) MacOS13.6.6 Firefox 125.01

Any idea what's going on?

This has been happening for months now, on multiple devices (I have tried at least 3 different devices), and on multiple networks.

I have read the articles in here, but they just want me to check network configuration which is exactly the same for all browsers.

If I restart firefox it starts working again.

How can I prevent it from breaking randomly? This is the only browser having issues, I'm almost positive is some bug and not a configuration thing, given that it happens under multiple circumstances and devices, while Edge and Chrome simply keep working just fine.

There is no consistent repro I can give, afaik it is just random, at some point Firefox just decides to stop working and I have to restart it. This disrupts my work and browsing activities as I can lose progress on input forms and similar actions.

I see my original question is now archived at https://support.mozilla.org/en-US/questions/1380948#question-reply I never closed it because I didn't know if my last process could really fix the issue. It didn't, not always. Over the years, there have been times when the issue would still pop up, but not as often as before (2022 and earlier).

I have a feeling that during an issue, FF is having difficulty setting up shop after starting up. Consequently, it is spending more time before it could become prepared to connect to the Net. I've come up with another "solution," which is deleting (or moving out) xulstore.json in the profile folder after exiting or before starting FF. You can create a batch command or script to execute the process.

So far, FF is connecting immediately after startup.

MacOS Sonoma 14.4 seems to have broken a number of apps. AFter updating to Sonoma 14.4 I experienced a great number of crashes with Thunderbird, so I completely uninstalled Thunderbird and removed all traces of plists, Application preferences, everything, reinstalled Thunderbird, and added back the two email accounts I use with it. It now takes up to 30 seconds to start up Thunderbird, after which it happily no longer crashes, but obviously the startup time is unacceptable. I experience the same problem with Typora, and the developers there informed me that they believe the problem is with a Sonoma change that broke WebKit. I don't know if Thunderbird still uses Gecko or if the new version is WebKit. Please let me know if other Sonoma users have reported this problem or if it's just my system.

An IMAP mail system is configured on a server running Debian 12. While there are never any problems via webmail, reception and sending work occasionally via Thunderbird 115.9. Even in "Troubleshooting Mode" it doesn't work. The server has good hardware characteristics and there are no applications that can slow it down, nor do I think it is a firewall problem or incorrect parameters otherwise it would never work. The error is related to timeout reaching the server. What can I check to find out where the problem is?

I reinstalled the Visual C++ and Firefox loaded when i ran the Firefox repair but totally locked up. Unable to get to settings or any website and will not run after closing it.