In what cases will Chrome disable extension?

[Juraj M.]

I've received some rare feedback that my extension is sometimes getting disabled and user needs to manually re-enable it.

(this is not related to updates nor policy issues)

I think I've seen this some years ago during development when my extension got stuck in some reload loop, and Chrome then disabled it.

Is this documented somewhere?

Also, any ideas how to debug or investigate such cases?

[woxxom]

• the extension's files got corrupted
• the user [accidentally] disabled the extension for New tab page or Search in the warning displayed by the browser "Do you want to keep this extension?"
• the extension was disabled on another device and its status got synced to this one
• the extension is added to Safe Browsing's graylist
• the extension's process has crashed (a bug in the browser or exceeding JS limits for memory/stack)
• the user terminated the extension's process in Task Manager
• another extension disabled yours

[Juraj M.]

Nice!

Thank you for the concise list :), I will be using this for much better support!

It would be great though if this was officially listed in the docs...

Should I maybe create a ticket for that?

(or maybe I'll just pray that Oliver will notice this and do it for me :)..., oh man, I'm so lazy / burned out sometimes...)