Reputation: 3238
In recent versions of Firefox (since 42 or 43 maybe?), I find some sites unusable due to NS_ERROR_STORAGE_CONSTRAINT errors. I currently have 43.0.4. For example, when I go to https://jsfiddle.net/, I get this:
NS_ERROR_STORAGE_CONSTRAINT:
var baseUrlOverride = localStorage.getItem("togetherjs.baseUrlOverride");
togetherjs.js (line 85)
NS_ERROR_STORAGE_CONSTRAINT:
...ing")};window.addEvent("domready",function(){var e=document.id("add_external_res...
_dist-e..._2016_1 (line 32)
NS_ERROR_STORAGE_CONSTRAINT:
...s(e.dataset.id),t.markReadItems()),t.pushMessage("setBadge",{counter:t.currentCo...
app.js (line 1)
and the site can't finish loading. This is just one example, there are many others. Pretty much any site that uses localStorage is giving these errors. I can't find any documentation that explains what this error is or how to fix it. Any ideas?
Upvotes: 25
Views: 11500
Reputation: 1105
For me just updating Firefox probably lead to a resolution (I also changed the localStorage
property value through the console and refreshed a page, but I'm not sure if that changed anything).
My current version: 126.0.1.
I understand it may not be as simple as that for others, but I believe just updating is worth a shot to maybe start with.
I also think that if one really opened the same profile in different Firefox versions (like stable and Nightly) and it caused the issue (or some other one), just making sure that both of them share the same Firefox version may lead to a resolution to the issue.
Upvotes: 0
Reputation: 1578
At least version 97, 98, and 99 of Firefox are affected by bug #1758416, which causes NS_ERROR_STORAGE_CONSTRAINT
to be returned by localStorage
operations.
The problem seems to empty strings being coerced to NULL
, when storing localStorage
data with SQLite and NULL
not being allowed for by Firefox's schema.
Upvotes: 2
Reputation: 938
I had to clear Cookies and Site Data
to fix this issue in Firefox 98.x.x (64-bit)
Go to Preferences
> Privacy & Security
> Cookies and Site Data
> Clear Data...
All other steps like deleting webappsstore.sqlite
file and fixing the profile did not work for me.
Upvotes: 22
Reputation: 3809
Same case happened to me. My Firefox Profile got corrupted. Here are steps I did to recover my profile:
about:profiles
pageRoot Directory
path. Open it in any file managerwebappsstore.sqlite
- remove it (this alone didn't help in my case, but might help in your case as others report here)storage/default/
directoryhttp
/https
/file
. Don't remove folders starting from moz-extension
unless you want to clean settings of your extensions tooI believe the main root cause in my case was parallel access by Google Drive app to the Profile directory. I wanted to have my Profile synced with cloud. It worked for quite some time, but at some point, the Profile got corrupted.
Upvotes: 7
Reputation: 1514
As the other answer says, your Firefox profile got corrupted. That is true, but you don't have to abandon your profile.
You have to find your profile on disk and delete webappsstore.sqlite
in that profile. This will clear all your saved site storage.
To avoid this from happening in the future make sure not to mix the same profile between Nightly / Developer Edition and Stable versions of Firefox.
The patches to fix this issue just landed and should be available soon.
Bugzilla Bug url: https://bugzilla.mozilla.org/show_bug.cgi?id=1240238
Upvotes: 14
Reputation: 3621
Your firefox' profile database is corrupted. You need to create a new profile using the Firefox ProfileManager.
Upvotes: 0