Bugzilla

So in the vast majority of cases we are not stuck in the child process in any `SpinEventLoopUntil` and we need to look out for other common patterns. :-(

There [are some cases though](https://crash-stats.mozilla.org/search/?signature=%3DIPCError-browser%20%7C%20ShutDownKill&build_id=%3E20211124000000&xpcom_spin_event_loop_stack=%21~default%3A&product=Firefox&date=%3E%3D2021-11-23T12%3A05%3A00.000Z&date=%3C2021-11-30T12%3A05%3A00.000Z&_facets=signature&_facets=xpcom_spin_event_loop_stack&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-xpcom_spin_event_loop_stack)

where we find ourselves stuck in [RequestHelper::StartAndReturnResponse](https://searchfox.org/mozilla-central/rev/4c184ca81b28f1ccffbfd08f465709b95bcb4aa1/dom/localstorage/LSObject.cpp#1227-1252) which might indicate some pitfall in the request/response flow of local storage.

The [remaining cases with an event loop stack from the parent process](https://crash-stats.mozilla.org/search/?signature=%3DIPCError-browser%20%7C%20ShutDownKill&build_id=%3E20211124000000&xpcom_spin_event_loop_stack=~default%3A&product=Firefox&date=%3E%3D2021-11-23T12%3A05%3A00.000Z&date=%3C2021-11-30T12%3A05%3A00.000Z&_facets=signature&_facets=xpcom_spin_event_loop_stack&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-xpcom_spin_event_loop_stack) are almost all happening during `nsThread:.Shutdown` for some thread.

So in the vast majority of cases we are not stuck in the child process in any `SpinEventLoopUntil` and we need to look out for other common patterns. :-(

There [are some cases though](https://crash-stats.mozilla.org/search/?signature=%3DIPCError-browser%20%7C%20ShutDownKill&build_id=%3E20211124000000&xpcom_spin_event_loop_stack=%21~default%3A&product=Firefox&date=%3E%3D2021-11-23T12%3A05%3A00.000Z&date=%3C2021-11-30T12%3A05%3A00.000Z&_facets=signature&_facets=xpcom_spin_event_loop_stack&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-xpcom_spin_event_loop_stack) 
where we find ourselves stuck in [RequestHelper::StartAndReturnResponse](https://searchfox.org/mozilla-central/rev/4c184ca81b28f1ccffbfd08f465709b95bcb4aa1/dom/localstorage/LSObject.cpp#1227-1252) which might indicate some pitfall in the request/response flow of local storage.

The [remaining cases with an event loop stack from the parent process](https://crash-stats.mozilla.org/search/?signature=%3DIPCError-browser%20%7C%20ShutDownKill&build_id=%3E20211124000000&xpcom_spin_event_loop_stack=~default%3A&product=Firefox&date=%3E%3D2021-11-23T12%3A05%3A00.000Z&date=%3C2021-11-30T12%3A05%3A00.000Z&_facets=signature&_facets=xpcom_spin_event_loop_stack&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-xpcom_spin_event_loop_stack) are almost all happening during `nsThread:.Shutdown` for some thread.

So in the vast majority of cases we are not stuck in the child process in any `SpinEventLoopUntil` and we need to look out for other common patterns. :-(

There [are some cases though](https://crash-stats.mozilla.org/search/?signature=%3DIPCError-browser%20%7C%20ShutDownKill&build_id=%3E20211124000000&xpcom_spin_event_loop_stack=%21~default%3A&product=Firefox&date=%3E%3D2021-11-23T12%3A05%3A00.000Z&date=%3C2021-11-30T12%3A05%3A00.000Z&_facets=signature&_facets=xpcom_spin_event_loop_stack&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-xpcom_spin_event_loop_stack) where we find ourselves stuck in [RequestHelper::StartAndReturnResponse](https://searchfox.org/mozilla-central/rev/4c184ca81b28f1ccffbfd08f465709b95bcb4aa1/dom/localstorage/LSObject.cpp#1227-1252) which might indicate some pitfall in the request/response flow of local storage.

The [remaining cases with an event loop stack from the parent process](https://crash-stats.mozilla.org/search/?signature=%3DIPCError-browser%20%7C%20ShutDownKill&build_id=%3E20211124000000&xpcom_spin_event_loop_stack=~default%3A&product=Firefox&date=%3E%3D2021-11-23T12%3A05%3A00.000Z&date=%3C2021-11-30T12%3A05%3A00.000Z&_facets=signature&_facets=xpcom_spin_event_loop_stack&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-xpcom_spin_event_loop_stack) are almost all happening during `nsThread:.Shutdown` for some thread.

So in the vast majority of cases we are not stuck in the child process in any `SpinEventLoopUntil` and we need to look out for other common patterns. :-(

There [are some cases though](https://crash-stats.mozilla.org/search/?signature=%3DIPCError-browser%20%7C%20ShutDownKill&build_id=%3E20211124000000&xpcom_spin_event_loop_stack=%21~default%3A&product=Firefox&date=%3E%3D2021-11-23T12%3A05%3A00.000Z&date=%3C2021-11-30T12%3A05%3A00.000Z&_facets=signature&_facets=xpcom_spin_event_loop_stack&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-xpcom_spin_event_loop_stack) where we find ourselves stuck in [RequestHelper::StartAndReturnResponse](https://searchfox.org/mozilla-central/rev/4c184ca81b28f1ccffbfd08f465709b95bcb4aa1/dom/localstorage/LSObject.cpp#1227-1252) which might indicate some pitfall in the request/response flow of local storage.

The [remaining cases with an event loop stack from the parent process](https://crash-stats.mozilla.org/search/?signature=%3DIPCError-browser%20%7C%20ShutDownKill&build_id=%3E20211124000000&xpcom_spin_event_loop_stack=~default%3A&product=Firefox&date=%3E%3D2021-11-23T12%3A05%3A00.000Z&date=%3C2021-11-30T12%3A05%3A00.000Z&_facets=signature&_facets=xpcom_spin_event_loop_stack&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-xpcom_spin_event_loop_stack) are almost all happening during `nsThread:.Shutdown` for some thread on the parent process.