4

Some of google chrome extensions have been corrupted constantly. In the period of 2 or 4 days, some extension's status are changed to "corrupted".

Then, I need to "Repair" every corrupted extensions. But, just a few days later, the situation repeats again and again and again..... During the period of time, nothing and no any single change makes for the google or computer at all. The extensions are just corrupted again and again... It is really annoying and wastes much time to repair.

What to do to prevent from it? Or, is there a way to "repair" all of corrupted extensions by clicking one single button?

Ray Kao
  • 93

2 Answers2

2

You have a much more serious problem than re-repairing all your extensions at once:

Why are they getting corrupted in the first place?

Corruption means that something is modifying your extensions, and this is entirely abnormal and even alarming.

The possibilities I can see are:

  1. Your computer is infected (seems possible)
  2. You have installed a rogue extension (less likely as extensions are sandboxed).
  3. Legit extensions but corrupted profile (bad data that causes some legit extension to act strangely).

For the second case, you could remove all extensions and add them one by one to check which one is doing it.

The first case is much more difficult. Read the following article for advice:
How can I remove malicious spyware, malware, adware, viruses, trojans or rootkits from my PC?

For the third and very rare case, start a new profile.

harrymc
  • 498,455
1

It could be Tampermonkey.

Encountered a similar issue when we made a TamperMonkey script that used persistent storage.

JasonXA’s comments above seem like a plausible explanation—the database is getting too big, and Chrome’s implementation is not stable.

Add one more culprit: recent use of LevelDB is unstable, since the issue was not present when Chrome used SQLite... if the db gets too large, they might be faster than SQLite but they will get corrupted. These db's are used to store mainly extension settings in the AppData ... Default (or Profile name) \ Local Extension Settings folder, each in a subfolder named per extension id. I was backing those up and restoring from the most recent backups, i.e. largest, but got corrupted again and again.

I proceed to export the settings where option was available, closed browser, removed the affected db, restarted browser and imported the settings again. So far no more corruption. uBO and TamperMonkey were among the affected with very large db files, 20MB+, for some reason. Right now uBO went under 12MB and TM is at 1.25MB. That's in case it's a localized issue and the user doesn't want to redo the whole profile.

Yatharth Agarwal
  • 672