Massive issues since most recent Firefox update.

jbr said

The privacy pref might have been set remotely for release; on nightlies it's added directly in code but only starting v153 (you should be able to just add it manually in advance /it's type "boolean"/ and then with the other prefs let that nightly update to latest — to see if those prefs have any effect for your system. If it doesn't work, you now know how to reset the nightly back to older version again;)…) As for downgrading a profile, there's a way around it, see https://support.mozilla.org/en-US/kb/dedicated-profiles-firefox-installation#w_what-happens-to-my-profile-if-i-downgrade-to-a-previous-version-of-firefox but please do BACKUP!! the profile folder first. Ideally to three different places.

I'll restart my Nightly first with these new privacy preferences & update it to see if it does anything different, and then try the new profile because I'm thinking if these work with Nightly, maybe I could go in and try the same changes to my regular Firefox and see if that's a potential fix...? I'll have to see if it changes anything in Nightly first, of course, and then see if I could even get my Firefox to work long enough to change those settings. And by backing up the profile folder, you mean the actual folder on my computer, correct?

So, after changing those privacy preferences I updated Nightly to the newest version (v155) and the same issue of the window opening then freezing happens, but something interesting is that this time it actually stayed working long enough for me to load up a tab before it froze up, and I noticed something else. In my task manager, under the details tabs, there’s only one Nightly process that is non-responsive, and in clicking on analyze wait chain, a window pops up that says ‘one or more threads of firefox.exe are waiting to finish network I/O’. Does that mean what’s happening is a network connectivity issue? Additional info: I went through all the Nightly processes and looked through their wait chains, and there was one other process that said the same thing, but it said it was running, but non-responsive. Not sure if any of this means anything.

Edit: After making these changes, I’ve noticed that both Firefox & Nightly start up very fast (almost immediately) and the time from them opening to freezing up has become a much longer period. I can load links and go putter around in settings for a few minutes before it ultimately freezes up which does still suck, but…progress? A little bit? Further edit: I’ve also since turned off DNS over HTTPS, and after doing so I’ve noticed it takes a lot longer for my Firefox to become non-responsive, usually ~5 minutes or so. It does still eventually freeze, but I feel like maybe that’s part of the issue…? I mean…I also don’t understand what disabling this does, but I figure it may be relevant to someone.

Ok, so those keys didn't actually fix things, but they changed something. Now FF doesn't actually hang completely. It will take a long time, but it will respond. I was checking the new SMBC comic and I got 4 console and network erros for talk.hyvor.com with http code 422. The console errors report after a few miliseconds, in the network tab they show up as taking over 10s each. Which is what is probably hanging FF. Google and youtube both have lots of requests taking over 3 minutes, but no relevant errors in the console (Youtube only has a CORS error).

I then tried checkin my addons (honestly, should have tried it earlier. When I turn them all off, things load fine, so I pinpointed Tampermonkey as the culprit (even though I don't have scripts for those pages, only for SMBC of the ones I tried). I'm not sure if this issue is actually related, but I've restored the values on the config keys and will keep an eye to see if it replicates with the addon disabled.

I have doubts this is the issue the rest of the people are having. Tampermonkey is kind of a specialized addon and not many people are bound to have it. Still, it's possible some other addon they have is causing it?

It's kinda annoying because Tampermonkey is a nice QoL for some sites I visit.

So, a new update: Even with Tampermonkey disabled (even though I turned it on for loading one page, but turned it off again) and with the keys restored, the issue persists. It should be noted even when FF is hanging it still loads mozilla pages (like this one and the profiler one) just fine.

Looking at the console/network, I get a bunch of NS_BINDING_ABORTED errors. I turned the profiler on and it generated this: https://profiler.firefox.com/from-browser/marker-chart/?globalTrackOrder=n0wm&hiddenGlobalTracks=1wl&hiddenLocalTracksByPid=5916-0~1992-0w2~12284-0w3~25124-0w2~13460-0w2~22508-01~20336-0w2~19836-0w4~1444-0w2~20140-0w2~11640-0w2~21080-0w2~19524-0w2~20404-0w2~11624-0w7~11660-0w3~12740-0w2~7128-0w3&thread=0&v=17

Does this help? Do you need more to find out what the issue is? Still want me to try out regression?

To share a profile you'd need to upload it first: https://profiler.firefox.com/docs/#/./guide-getting-started?id=share-a-profile — that will give you a shortlink that's ready for sharing.

Ideally when you still reproduce in Nightly, it's better to file a bug, add the profile captured, and if you can easily tell "good" vs. "bad" then also run the mozregression to see if it can provide the range (pushlog) of changes that are the suspected difference that's having impact on your experience.

If, conversely, you'd like to try flipping prefs in your current release, I'd start with something like disabling http3 or tls versions — it seems it's connection related to some extent.

To share a profile you'd need to upload it first: https://profiler.firefox.com/docs/#/./guide-getting-started?id=share-a-profile — that will give you a shortlink that's ready for sharing. Ideally when you still reproduce in Nightly, it's better to file a bug, add the profile captured, and if you can easily tell "good" vs. "bad" then also run the mozregression to see if it can provide the range (pushlog) of changes that are the suspected difference that's having impact on your experience. If, conversely, you'd like to try flipping prefs in your current release, I'd start with something like disabling http3 or tls versions — it seems it's connection related to some extent.

I managed to recreate a new profiler. This is with tampermonkey active, since I think that would be more useful, as I'd like to keep using it. https://share.firefox.dev/4x3Z0hh

Tomorrow I'll look into mozregression.

To share a profile you'd need to upload it first: https://profiler.firefox.com/docs/#/./guide-getting-started?id=share-a-profile — that will give you a shortlink that's ready for sharing. Ideally when you still reproduce in Nightly, it's better to file a bug, add the profile captured, and if you can easily tell "good" vs. "bad" then also run the mozregression to see if it can provide the range (pushlog) of changes that are the suspected difference that's having impact on your experience. If, conversely, you'd like to try flipping prefs in your current release, I'd start with something like disabling http3 or tls versions — it seems it's connection related to some extent.

(some weird stuff happened, not sure if I'm double posting). I managed to create another profiler log (the previous one was unavailable). This is with Tampermonkey active, since that would seem more useful, as I'd like to keep using it. https://share.firefox.dev/4x3Z0hh