Bugzilla

I've had another pass at the crashes and I'm now convinced that this is just content processes being slow during shutdown. Here's why: many crashes have the `IPCShutdownState` annotation set to `RecvShutdown` which is consistent with the stack we see here - shutdown has begun but not finished yet. However the vast majority of the crashes have that annotation set to `SendFinishShutdown (sent)` which happens [past the point](https://hg.mozilla.org/mozilla-central/annotate/114d8b270dbb4d512650b3918b87d71dbc83ad50/dom/ipc/ContentChild.cpp#l3090) where this stack trace originates from.

Since the minidump and the annotations are not perfectly in-sync it's possible that in most cases we grabbed a minidump, and by the time we grabbed the annotations the content process had made forward progress already. Jed if you agree with this analysis feel free to close this as invalid and move the signatures to bug 1279293 since this is just generic slowness and not something we can act upon directly.

I've had another pass at the crashes and I'm now convinced that this is just content processes being slow during shutdown. Here's why: many crashes have the `IPCShutdownState` annotation set to `RecvShutdown` which is consistent with the stack we see here - shutdown has begun but not finished yet. However the majority of the crashes have that annotation set to `SendFinishShutdown (sent)` which happens [past the point](https://hg.mozilla.org/mozilla-central/annotate/114d8b270dbb4d512650b3918b87d71dbc83ad50/dom/ipc/ContentChild.cpp#l3090) where this stack trace originates from.

Since the minidump and the annotations are not perfectly in-sync it's possible that in most cases we grabbed a minidump, and by the time we grabbed the annotations the content process had made forward progress already. Jed if you agree with this analysis feel free to close this as invalid and move the signatures to bug 1279293 since this is just generic slowness and not something we can act upon directly.