Skip to content
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

Closed
kamilion opened this issue Mar 2, 2018 · 8 comments
Closed

QUOTA_BYTES quota exceeded #1902

kamilion opened this issue Mar 2, 2018 · 8 comments

Comments

@kamilion
Copy link

kamilion commented Mar 2, 2018

badger

As requested, here is your issue report.

Now, how do I make it go away?

@ghostwords
Copy link
Member

ghostwords commented Mar 2, 2018

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 chrome://extensions, make sure "Developer mode" is checked, click on the "background page" link in Privacy Badger's row, and select the Console tab.

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));
}());

@kamilion
Copy link
Author

kamilion commented Mar 2, 2018

First one returns 4.91 MB,
Second one returns:
"base": "pubnub.com",
"count": 35576,
"base": "googlevideo.com",
"count": 553,
"base": "disqus.com",
"count": 549,
"base": "wordpress.com",
"count": 179,
"base": "photobucket.com",
"count": 158,
"base": "google.com",
"count": 86,
"base": "alicdn.com",
"count": 54,
"base": "akamaihd.net",
"count": 45,
"base": "tinypic.com",
"count": 44,
"base": "googleusercontent.com",
"count": 32,

@ghostwords
Copy link
Member

ghostwords commented Mar 2, 2018

Oh wow, I think we know what the problem is, it's pubnub.com. Well, it's really the combination of #888 and #1864.

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 pubnub.com:

(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 chrome://extensions or by restarting the browser) helps.

@kamilion
Copy link
Author

kamilion commented Mar 2, 2018

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.

pbadger.json.gz

@ghostwords
Copy link
Member

ghostwords commented Mar 2, 2018

OK, thanks for following up! Closing this as the fix is tracked in #1864. Let me know if this comes up again.

@kamilion
Copy link
Author

kamilion commented Mar 2, 2018

What's the best method to whitelist the noisy-named domains cleanly?
*.pubnub.com on it's own line?
I can remove it in six months or a year.

@ghostwords
Copy link
Member

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);

@alwaysontheice
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants