FireFox crashes on startup - even in safe mode - with reportID inside
- Had 3 windows open with numerous tabs and tab groups - Firefox sync was enabled, as well as a 2-3 plugins AFAIK - Version installed is latest as of this writing 139.0.4 - Initial crash caused by opening and quickly closing (IF that succeeded before crash) a onedrive share link - Cannot start firefox any more, also not in safe mode - the only thing that works is launching it with a fresh profile.
The report ID is bp-a8c824fc-a7fb-4290-a72b-b63160250620
Ideally I can resolve this without needing to refresh or start over with a new profile
Ŋuɖoɖo si wotia
Hi Sintel, your crash report's Bugzilla tab links to a bug that is fixed in Firefox 140 (1971020), but did not make it into any of the minor updates for Firefox 139. Firefox 140 is due for release on Tuesday, June 24th.
(The following is based on reading the bug report and patch.)
The change made by the bug is fairly straightforward, but if Firefox won't run, it's difficult to implement because you can't just go into about:config and toggle network.cookie.chips.partitionLimitDryRun to true.
You could try to do it by creating a user.js file. A user.js file is a plain text file with a .js extension that you place in your active profile folder. The command you would add to the file is simply this:
user_pref("network.cookie.chips.partitionLimitDryRun", true);
You would only need this temporarily until you get Firefox 140.0 next week.
The other thing that comes to mind is, if the problem is related to cleaning cookies, would you be willing to temporarily remove the cookies.sqlite database so that Firefox doesn't have any cookies to clean up and see whether Firefox will run? You could rename the file to cookiesOLD.sqlite or move it to a different folder until Firefox can use it again. Unfortunately, the side effect is being logged out of everything.
In case you are interested in either of these experiments, this article describes how to locate your profile folder on Mac OS when Firefox won't run: Profiles - Where Firefox stores your bookmarks, passwords and other user data.
Xle ŋuɖoɖo sia le goya me 👍 0All Replies (1)
Ɖɔɖɔɖo si wotia
Hi Sintel, your crash report's Bugzilla tab links to a bug that is fixed in Firefox 140 (1971020), but did not make it into any of the minor updates for Firefox 139. Firefox 140 is due for release on Tuesday, June 24th.
(The following is based on reading the bug report and patch.)
The change made by the bug is fairly straightforward, but if Firefox won't run, it's difficult to implement because you can't just go into about:config and toggle network.cookie.chips.partitionLimitDryRun to true.
You could try to do it by creating a user.js file. A user.js file is a plain text file with a .js extension that you place in your active profile folder. The command you would add to the file is simply this:
user_pref("network.cookie.chips.partitionLimitDryRun", true);
You would only need this temporarily until you get Firefox 140.0 next week.
The other thing that comes to mind is, if the problem is related to cleaning cookies, would you be willing to temporarily remove the cookies.sqlite database so that Firefox doesn't have any cookies to clean up and see whether Firefox will run? You could rename the file to cookiesOLD.sqlite or move it to a different folder until Firefox can use it again. Unfortunately, the side effect is being logged out of everything.
In case you are interested in either of these experiments, this article describes how to locate your profile folder on Mac OS when Firefox won't run: Profiles - Where Firefox stores your bookmarks, passwords and other user data.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.