Firefox Crashing After Closing when Sync Enabled
I recently switched to Linux on both my laptop and desktop computers, and I have started having an issue where after closing Firefox, the process does not end fully, leading to a Firefox crash notice after a minute or two.
This seems to only happen when I have sync turned on. It always says "syncing..." and never finishes, and logging out of my account or turning sync off fixes this problem. However, I'd really like to be able to use sync across my two systems.
My laptop is running Pop OS, and my desktop is running CachyOS. Making a new account fixed this error for a few days, and now it is happening again.
Here is my newest crash report: https://crash-stats.mozilla.org/report/index/9adbdc82-3cfa-49b7-8bad-e6e590260319
All Replies (3)
Hello,
Here are some ways to troubleshoot it : 1. Delete Sync and Profile files Go to your Firefox profile folder about:support and delete compatibility.ini and places.sqlite files.
2. Reset Firefox Sync Turn off Sync, restart Firefox, and sign back in to force a fresh data sync.
3. Update and Reinstall Make sure you have the latest version of Firefox. Sometimes, a full uninstall and a new download from Mozilla, is required to fix it.
4. Check for Corruption Use the about:support page to check for profile corruption or run Firefox in Troubleshoot Mode to rule out extension conflicts.
5. Restart your computer (self explanatory)
What desktop? X11 or wayland? Try downloading Firefox from Mozilla. Download, unzip, and run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
Has been working for me.
Modified
You can open about:sync-log via the location bar to see if recent Sync logs are available. You can upload the file to a website if you can't post the content of the file in a reply.
You can temporarily toggle this pref to true in about:config to get a Sync log in case of success to check how Sync performs.
- services.sync.log.appender.file.logOnSuccess => true
Do not forget to reset services.sync.log.appender.file.logOnSuccess after you are done testing.