-
-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QUOTA_BYTES quota exceeded #1902
Comments
Hello! Thanks for reporting your problem. Could you run the following code in your Badger's background page and let me know what gets printed? To get to the background page console in Chrome, visit Let me know if you have any questions. This should print how much space your Badger uses: chrome.storage.local.get(null, r=>console.log(
parseFloat(JSON.stringify(r).length / 1024 / 1024).toFixed(2), "MB")); This should print what your most populous domains are: (function () {
let action_map = badger.storage.getStore('action_map').getItemClones();
let result = _.chain(Object.keys(action_map))
.countBy(domain => getBaseDomain(domain))
.map((v, k) => {
return {
base: k,
count: v
};
})
.sortBy('count')
.reverse()
.slice(0, 10)
.map(i => {
i.domains = _.filter(Object.keys(action_map), d => d.endsWith(i.base));
return i;
})
.value();
console.log(JSON.stringify(result, null, 2));
}()); |
First one returns 4.91 MB, |
Oh wow, I think we know what the problem is, it's As a workaround for now (this problem may come back until we take care of #1864), you can run the following code in your Badger's background page to make it forget about (function () {
let am = badger.storage.getStore('action_map');
for (let domain in am.getItemClones()) {
if (window.getBaseDomain(domain) == "pubnub.com") {
am.deleteItem(domain);
}
}
}()); Let me know if running the code and restarting Privacy Badger (by clicking Reload on |
4.91MB -> 1.33MB. Here's the dump, with the disqus and wordpress entries removed for privacy. I am in Silicon Valley, if that helps as a georeference for the listed servers. |
OK, thanks for following up! Closing this as the fix is tracked in #1864. Let me know if this comes up again. |
What's the best method to whitelist the noisy-named domains cleanly? |
What do you mean by "whitelist"? Correction to #1902 (comment), there is a better workaround you can run in the background page that will remove all domains that shouldn't have been recorded: require("migrations").Migrations.forgetNontrackingDomains(badger); |
I just encountered this same issue except with a Google AdSense domain: *.googlesyndication.com. Following the above steps (but changing the domain) allowed me to remove thousands of entries. Not sure what caused the issue in the first place. |
As requested, here is your issue report.
Now, how do I make it go away?
The text was updated successfully, but these errors were encountered: