excessive browser.cache.disk.capacity

[noemata]

hi,

the browser.cache.disk.capacity reverts  always to value =  1048576 after changing browser.cache.disk.capacity to a much lower parameter (1048576 is imho really too much), only when the addon is activated. so the excessive cache parameter is modified by the addon itself. only if i set browser.cache.disk.smart_size.enabled to false, it is possible to set up the cache to the default, more moderate parameter (256000).

is the excessive use of the ff browser cache by design or a bug?

 

sincerely, noe

Edited August 13, 2018 by noemata

[rakka]

Hi There,

We are using 1MB of cache to store the DB, which is by designed and required in order for extension to function. 

[noemata]

50 minutes ago, rakeshsejwal said:

Hi There,

We are using 1MB of cache to store the DB, which is by designed and required in order for extension to function. 

thx for your fast answer, 2 more/last questions:

only 1mb .. smart.

1) but why then the excessive cache parameter (about:config,  browser.cache.disk.capacity) of 1048576 kb ,  modified by the addon? this slows down the browser over time. one have always to manually delete the cached web content (because of the addon, it is not possible to set the standard value (without "browser.cache.disk.smart_size.enabled" to "false")).

2) so as a workaround, i can set browser.cache.disk.smart_size.enabled to false & browser.cache.disk.capacity to the default value (256000 kb) without any side effects & full addon-functionality?

sincerely,

noe (ff 62 beta 16, privacy.firstparty.isolate enabled)

Edited August 13, 2018 by noemata

[exile360]

I'm guessing perhaps there is a bug where a 0 has been misplaced by mistake.  If you check the math (1024KB=1MB, 1024MB=1GB), 1048576KB\1024=1024MB (or exactly 1GB) while the default, 256000KB\1024=250MB (or exactly 25% of 1GB) and I'm guessing that whoever coded the plugin configured it to reserve 1MB minimum but instead accidentally set it at 1GB minimum.

That's just my theory however, but the math would appear to validate my hypothesis.

Edited August 18, 2018 by exile360

[noemata]

thx exile360, math is always right. completely comprehensible argument. so, it's a bug  ( @mwb - team . plz fix it. )

 

Edited August 18, 2018 by noemata

[exile360]

Yep, I bet they meant to set the reserved amount of space to 1024kb (1MB) but accidentally set it to 1024mb (1GB) instead.  I'll report it to the team for review and hopefully they'll have it fixed promptly in an upcoming release.

[Swandog46]

We are not setting any browser-wide settings, no cache size setting, nothing.  The extension uses about 5 MB of disk space to store its internal data files, but that is not in the browser cache (which is reserved for website data), it's in a dedicated database that the browser allocates to the extension.  (You can see the files under AppData, I forget exactly where it's located for Firefox, but for Chrome it's under a folder called IndexedDB.)  What made you think that setting is being changed by our extension?

[noemata]

59 minutes ago, Swandog46 said:

We are not setting any browser-wide settings, no cache size setting, nothing.  The extension uses about 5 MB of disk space to store its internal data files, but that is not in the browser cache (which is reserved for website data), it's in a dedicated database that the browser allocates to the extension.  (You can see the files under AppData, I forget exactly where it's located for Firefox, but for Chrome it's under a folder called IndexedDB.)  What made you think that setting is being changed by our extension?

 

ok, now i am really disturbed .. what i did:

 

1. about:config?filter=browser.cache.disk.capacity

2. the value is modified & too high

3. reset the value to default

4. open a website

5. reload about:config?filter=browser.cache.disk.capacity

6. modified again,  value too high

7. disable the mbw - addon in about:addons completely

8. about:config?filter=browser.cache.disk.capacity

9. reset the value to default again

10. open a website

11. reload about:config?filter=browser.cache.disk.capacity

12.  and now .. the modified high value .. again .. although the mwb - addon is disabled.

 

but i could swear,  in my previous attempts around august 13th (previous mwb - beta version & previous ff beta version), the value did not changed again and remained at default (only) when the mwb - addon was disabled. but if my perception has played a trick on me, i am truly sorry to waste your time. i'm really confused now .

Edited August 20, 2018 by noemata

[Swandog46]

Definitely not wasting our time, don't worry.  For what it's worth, I just installed Firefox fresh and about:config showed a modified browser.cache.disk.capacity (to your same value 1048576), and that was without any extensions installed at all and a completely fresh install of the browser.  Not sure what's causing it, but I'm pretty sure it's not us... 

[GP45]

My own browser.cache.disk.capacity   always shows the value = 51200

Firefox Quantum 61.0.2 (64 bit)

[noemata]

gp45 & co . :

https://bugzilla.mozilla.org/show_bug.cgi?format=default&id=1257404

browser.cache.disk.smart_size is enabled just means that firefox/the browser itself decides/modifies the value. the value is then related to the respective system. unfortunately, i do not know on which exact criteria this automated ("smart") process is based on. but this is a "firefox thing". it has nothing to do with the mwb - addon itself. really sry @swandog46 & thx, because you pushed me to do the steps again - with a surprising end. and your math @exile360, was still comprehensible . thx for reporting my 2 affairs anyway.

 

Edited August 21, 2018 by noemata

[Swandog46]

No worries, and thanks for your detective work!