If that’s the case, trying to find the errant setting could be like looking for a needle in a haystack. Why not backup your whole profile? Because, it could be very possible that your freezing problem with FF may be the result of a new behavior that’s programmed into FF that’s conflicting with one of the myriad of policies/settings in about:config. BUT before proceeding, find a way to backup things like your bookmarks and your settings within the settings menus. Since your copy of FF is freezing, perhaps a refresh would help. SO, although I am not using Linux, and my copies of FF 102 aren’t freezing, I feel that your problem and mine may be somehow related, since they’re both FF 102.release versions. I did this about 10 or 12 times, enough that I hope I got their attention. I got prompted for the refresh by the FF uninstall routine when I selected the uninstall option in Windows’ Control Panel.īefore doing the refresh, I was letting FF’s crash reporter gather the needed data and submit it to Mozilla, in the hopes they’d look at it and figure out a fix for it soon. On the machine that FF crashed on shutdown on, I wound up doing a refresh instead of an uninstall, and that took care of it for me, BUT I had to go in and reconfigure the about:config preferences I’d customized over the years. The other machine with FF 102 doesn’t crash on shutdown, but it does hog up to 40% of CPU clock cycles while it shuts down and takes about 30 seconds to do so. I’m using Windows, not Linux, BUT have been experiencing crashes on shutdown from FF 102 ever since upgrading to it last Wednesday or Thursday on one of my machines.
0 kommentar(er)
