[cross-posting to dev-platform] IPCError-browser | ShutDownKill crashes are the second most common ones after OOMs and generally not actionable because we've been lumping together a bunch of different stacks under the same signature.
These crashes represent a snapshot of a content process taking too long
to shut down. The affected content process is killed right after the
crash report is generated.
Bug 1612569 [1] will change those signatures soon. The new signatures
will include one or more function names after `IPCError-browser |
ShutDownKill` coming from the stack of the content process.
This will allow us to find common causes of slowness (or deadlocks) that
prevent content processes from shutting down rapidly and hopefully act
on them.
Gabriele
[1] Improve IPCError-browser | ShutDownKill signatures
https://bugzilla.mozilla.org/show_bug.cgi?id=1612569
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
