Could you please provide the crash ID from chrome://crashes for further investigation.

Please, read the report -
Crashed report ID: Nope, they are not generated for extension process crashes. See issue 147118 :(

Hmm, it's possible this might be Issue 642794 (browser process decides to terminate renderer due to getting a "bad" message from it).

phistuck - does this extension use executeScript? If so, it would be interesting to see if you could do something like wrap calls to executeScript with some code to write out a log entry (in localstorage/chrome.storage.local/indexeddb etc.) both before and after the executeScript call. What we might expect to see if this indeed is Issue 642794 is a log message telling us an executeScript call was about to be made but without a corresponding log message telling us the call finished. 

> does this extension use executeScript?
The extension code is attached to this issue (comment 0).
Anyway, I do not use executeScript. I use a simple content script.

I've confirmed that, at least on mac, we do indeed generate crash reports for extensions that crash due to things like segfaults, CHECKs, etc (I had some trouble getting an official build on Linux, but unofficial builds seem to confirm -- I'll see if I can't check Windows next).  But this seems in line with the thinking that this isn't the renderer process crashing so much as Chrome killing it, which doesn't generate a report (in the same way that killing an extension process through the Chrome task manager doesn't).

phistuck, can you do me a favor and next time this happens, check out chrome:histograms and see if you have an entry for "Extensions.BadMessageFunctionName", and, if so, what the values are?  If we are just killing the function, it would hopefully end up there.

I will upgrade to Chrome 53 and hope this never happens again. If it does, I will report back with the histogram data.

I am sorry for the late response.

Since I updated to Chrome 53, I believe this has happened more consistently. I usually hibernate (in the Windows-shutdown-mode sense) the machine daily. I think the extension crashed every time I turned the computer on (and Chrome was running when I hibernated) since I updated Chrome.

I do not see an entry for Extensions.BadMessageFunctionName, unfortunately.

Since updating to Chrome 54 (a week or two?), it only happened once.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

phistuck, are you still able to reproduce this? The last report is more than two years old.

It was so long ago I had a hard time remembering this even happened in the first place. Anyway, it has not reproduced for a long, long time.