The direction of duping is not 100% clear to me, but this seems to be the same as bug 1505660 and/or bug 1524247. Basically we get into late XPCOM shutdown and [the main thread hangs here](https://searchfox.org/mozilla-central/rev/759872688df15a5d6ab305ffe39d90450590bfec/xpcom/build/XPCOMInit.cpp#653), which [makes us wait here](https://searchfox.org/mozilla-central/rev/759872688df15a5d6ab305ffe39d90450590bfec/xpcom/threads/nsThreadManager.cpp#372-382) until all threads close promises resolve. In the stack traces I looked at, all threads seemed to be idling, when this happens, which would indicate that something goes wrong. This kind of crashes always existed, but I see some recent changes around canceling pending delayed runnables in bug 1695580 that might be related to the latest spikes and/or in the hope that :pehrsons knows more about this code.
Bug 1704391 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The direction of duping is not 100% clear to me, but this seems to be the same as bug 1505660 and/or bug 1524247. Basically we get into late XPCOM shutdown and [the main thread hangs here](https://searchfox.org/mozilla-central/rev/759872688df15a5d6ab305ffe39d90450590bfec/xpcom/build/XPCOMInit.cpp#653), which [makes us wait here](https://searchfox.org/mozilla-central/rev/759872688df15a5d6ab305ffe39d90450590bfec/xpcom/threads/nsThreadManager.cpp#372-382) until all threads' close promises resolve. In the stack traces I looked at, all threads seemed to be idling, when this happens, which would indicate that something goes wrong. This kind of crashes always existed, but I see some recent changes around canceling pending delayed runnables in bug 1695580 that might be related to the latest spikes and/or in the hope that :pehrsons knows more about this code.
The direction of duping is not 100% clear to me, but this seems to be the same as bug 1505660 and/or bug 1524247. Basically we get into late XPCOM shutdown and [the main thread hangs here](https://searchfox.org/mozilla-central/rev/759872688df15a5d6ab305ffe39d90450590bfec/xpcom/build/XPCOMInit.cpp#653), which [makes us wait here](https://searchfox.org/mozilla-central/rev/759872688df15a5d6ab305ffe39d90450590bfec/xpcom/threads/nsThreadManager.cpp#372-382) until all threads' close promises resolve. In the stack traces I looked at, all threads seemed to be idling when this happens, which would indicate that something goes wrong. This kind of crashes always existed, but I see some recent changes around canceling pending delayed runnables in bug 1695580 that might be related to the latest spikes and/or in the hope that :pehrsons knows more about this code.
The direction of duping is not 100% clear to me, but this seems to be the same as bug 1505660 and/or bug 1524247. Basically we get into late XPCOM shutdown and [the main thread hangs here](https://searchfox.org/mozilla-central/rev/759872688df15a5d6ab305ffe39d90450590bfec/xpcom/build/XPCOMInit.cpp#653), which [makes us wait here](https://searchfox.org/mozilla-central/rev/759872688df15a5d6ab305ffe39d90450590bfec/xpcom/threads/nsThreadManager.cpp#372-382) until all threads' close promises resolve. In the stack traces I looked at, all threads seemed to be idling when this happens, which would indicate that something goes wrong. This kind of crashes always existed, but I see some recent changes around canceling pending delayed runnables in bug 1695580 that might be related to the latest spikes so ni also in the hope that :pehrsons knows more about this code.