Bug 1279293 Comment 190 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

So looking at the [first reports from build 20220210213101](https://crash-stats.mozilla.org/signature/?build_id=%3E%3D20220210213101&signature=IPCError-browser%20%7C%20ShutDownKill&date=%3E%3D2022-02-04T12%3A51%3A00.000Z&date=%3C2022-02-11T12%3A51%3A00.000Z#aggregations) with the new annotations from bug 1754208, the interesting things is that we do not see any of them:

```
 1 	SendFinishShutdown (sent) 	7 	21.88 %
```

So there is a significant 78% of cases where we do not even reach [`RecvShutdown`](https://searchfox.org/mozilla-central/rev/81c52abeec336685330af5956c37b4bcf8926476/dom/ipc/ContentChild.cpp#3011-3013) at all, it seems.

IIUC all starts [here in the parent process](https://searchfox.org/mozilla-central/rev/81c52abeec336685330af5956c37b4bcf8926476/dom/ipc/ContentParent.cpp#1769-1778) and there are indeed (intentional) ways to call that function without sending the shutdown message to the child. It feels a bit odd that we apparently did not give the child any chance to shutdown and then just kill it, or am I overlooking something?
So looking at the [first reports from build 20220210213101](https://crash-stats.mozilla.org/signature/?build_id=%3E%3D20220210213101&signature=IPCError-browser%20%7C%20ShutDownKill&date=%3E%3D2022-02-04T12%3A51%3A00.000Z&date=%3C2022-02-11T12%3A51%3A00.000Z#aggregations) with the new annotations from bug 1754208, the interesting thing is that we do not see any of them:

```
 1 	SendFinishShutdown (sent) 	7 	21.88 %
```

So there is a significant 78% of cases where we do not even reach [`RecvShutdown`](https://searchfox.org/mozilla-central/rev/81c52abeec336685330af5956c37b4bcf8926476/dom/ipc/ContentChild.cpp#3011-3013) at all, it seems.

IIUC all starts [here in the parent process](https://searchfox.org/mozilla-central/rev/81c52abeec336685330af5956c37b4bcf8926476/dom/ipc/ContentParent.cpp#1769-1778) and there are indeed (intentional) ways to call that function without sending the shutdown message to the child. It feels a bit odd that we apparently did not give the child any chance to shutdown and then just kill it, or am I overlooking something?

Back to Bug 1279293 Comment 190