CODEWITHSUNDEEP
google-chromegoogle-chrome-extension
kentobi
kentobi

Reputation: 491

My extension's "Local Extension Settings" Logfile gets too big

I wrote the chrome extension View Later: click

A user reported, that there is a log file that gets way too big (his was around 3.8GB) that is located at C:\Users\<YOUR_USERNAME>\AppData\Local\Google\Chrome\User Data\Default\Local Extension Settings\hnolaplfoobcmgfmjphkmbjolinelpkb.

I immediately checked at my machine and it was big as well (~300mb). I do not know what is causing this. I use the chrome.storage heavily in my extension (all url's are saved there) but I do not know how this can get so big, as the limit is 512 entries to my knowledge.

Anyone got clues on this?
Thanks!

Upvotes: 5

Views: 6918

Answers (3)

Sungguk Lim
Sungguk Lim

Reputation: 6228

Interesting.

if the log file is a result of chrome.storage.

it looks like a bug. chrome.stoage.{local, sync} has a limit of quota.

Thank you for the bug reporting btw.

Upvotes: 0

Xan
Xan

Reputation: 77551

This seems to be a log of all storage events.

No idea why Chrome keeps it, and I don't think you can do anything to clean it.

It sounds like a bug worth reporting (why is this logging on, and what's the cutoff?).

Upvotes: 2

Oleg
Oleg

Reputation: 23297

It looks like you get favicons for saved URLs via http://www.google.com/s2/favicons?domain_url= service, convert them into Base64, and store in Local Storage. It might cause the problem.

Instead, you may try not to save them, but load http://www.google.com/s2/favicons every time user opens the Popup.

Upvotes: 1

Related Questions