Firefox 96 crashes made downgrade to 95.02 fail too, even after HTTP3 fix
This is what I’ve already reported (via Twitter to @FirefoxSupport, see https://twitter.com/quiet_listening/status/1481598382942703616). Read several support threads, tried the http3 fix (as indicated via e.g. https://support.mozilla.org/en-US/questions/1364124), but without any success.
Wubrane rozwězanje
Hi FredMcD, The past few days I've been mostly away from the keyboard. However, I picked up the 96.02 update, but had to postpone trying out your recipe. Now I sat down to try it out. But before I would try anything I did another check if the Sync'inc status had changed – AND IT HAD! Things seem to be very much are back to normal, including my all-important accounts/Saved Logins and Passwords. Anyway I THANK YOU so much for your help! :-)
Toś to wótegrono w konteksće cytaś 👍 0Wšykne wótegrona (8)
Need you to know this as well: Now (on January 16th 2022) I’ve applied the 96.01 upgrade patch. But sync does still not work, guys…
In the address box, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.
Please, Do not post a screenshot ! !
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
Hi FredMcD, When I execute the about:crashes command I get a list of 4x Unsubmitted Crash Reports, as well as a single Submitted one. But all of these were dated back in 2021, so not relevant I guess? The reason why I referred to what happened is because I used the macOS Activity Monitor (similar to Windows Taks Manager) to identify the Firefox process and kill/stop it manually/by myself, because it had reached the "not responding" state (text displayed in red, while the CPU utilization on one-or-two CPU core(s) went close to 100%). This happened repeatedly. Is there anyway else I can contribute relevant information?
BTW: I've submitted the unsubmitted ones.
The only thing not working now is the Sync feature. But (as I've pointed out earlier) this is crucial to me.
André Torkveen said
I execute the about:crashes command . . . But all of these were dated back in 2021
They would be of little use.
Use these links to create a new profile.
Use this new profile as is. Is the problem still there?
https://support.mozilla.org/en-US/kb/how-run-firefox-when-profile-missing-inaccessible
http://kb.mozillazine.org/Profile_folder_-_Firefox#Navigating_to_the_profile_folder
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles
Type about:profiles<enter> in the address box.
Wubrane rozwězanje
Hi FredMcD, The past few days I've been mostly away from the keyboard. However, I picked up the 96.02 update, but had to postpone trying out your recipe. Now I sat down to try it out. But before I would try anything I did another check if the Sync'inc status had changed – AND IT HAD! Things seem to be very much are back to normal, including my all-important accounts/Saved Logins and Passwords. Anyway I THANK YOU so much for your help! :-)
Glad to help. Safe Surfing.