Debugging extension crashes

[Nicole Tan]

Hey,

We've noticed user reports seeing this dialog "[Extension] has crashed. Click this balloon to reload the extension." but are unable to reproduce it. 

We've tried throwing an unhandled error in the background and setting multiple megabytes of data in local storage but didn't see the extension crash. 

Does anyone know what triggers this dialog? How can we add logging/error handling to catch this when it happens?

Thanks!

Nicole

[wOxxOm]

Usually it's when the extension creates an object too big to fit in JS memory heap or it's a bug in the browser.

[Oliver Dunk]

Hi Nicole,

Are you able to see a crash at chrome://crashes on one of the affected machines? If so, can you make sure that is uploaded, and send the crash ID?

As wOxxOm mentioned, there are a number of possible causes of this, but with that ID we should be able to look at the stack trace and figure out if this is an existing bug or a new one.

Thanks,

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/253d999c-8c18-45b2-8767-5d3347c89952n%40chromium.org.