How do you debug a Chrome extension crashing?

[Harry Qi]

Hey all! There have been a couple time where our extension crashed for a user, causing it to get disabled on the user's browser (see attached for what the user sees - a reload button). 

What are best practices in trying to debug what caused a crash? Does Chrome have any logs for it? 

Thanks so much!

[Joel Dart]

We had some issues a few years back. We used our own diagnostic logging (writing debug breadcrumbs locally) and then had the customer send us the logs once it reproduced. This helped us narrow down the rep steps. Once you have rep steps, you can get more information by running chrome with flags: http://dev.chromium.org/for-testers/enable-logging

Last time I was able to get what I needed to resolve it from there, but it should be noted that the stack trace itself for the crash itself wasnt available with just that. I'd found https://groups.google.com/a/chromium.org/forum/#!topic/chromium-extensions/gwEjc64aaPM which lead me to http://www.chromium.org/blink/getting-started-with-blink-debugging#TOC-Use-Chromium-s-StackTrace but I never took this all the way (this was also in 2015, so things could have changed by now). 

Hope this helps