These don't make a lot of sense, the content process (and in some cases the thumbnail process) fail to shutdown for an unknown reason. These children are sitting idle in the native message dispatch loop and are not hung. https://crash-stats.mozilla.com/search/?product=Firefox&signature=%3DIPCError-browser%20%7C%20ShutDownKill&proto_signature=~NtWaitForMultipleObjects%20%7C%20WaitForMultipleObjectsEx%20%7C%20MsgWaitForMultipleObjectsEx%20%7C%20mozilla%3A%3Awidget%3A%3AWinUtils%3A%3AWaitForMessage&_facets=signature&_facets=proto_signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-proto_signature
Looking at a few browser stacks, it looks like a lot of these may be triggered by browser side shutdown delays, which cause the child side shutdown timer to timeout.
For example: http://bsmedberg.github.io/socorro-toolbox/html/multiple-minidumps.html?crashID=71a34cb3-73ee-4095-b1d2-b6edf2160602 We should do more analysis on the stacks here to find common scenarios.
These don't block rollout.
tracking-e10s: ? → +
Priority: -- → P1
You need to log in before you can comment on or make changes to this bug.