(In reply to Mike Cloaked from comment #14) > The 15 seconds shutdown time remains the case with 106.0b1 where the console message is back: From [the profile it seems](https://share.firefox.dev/3RQZpzA) Thunderbird is stuck inside [`nsMsgAccountManager::CleanupOnExit`](https://hg.mozilla.org/comm-central/file/tip/mailnews/base/src/nsMsgAccountManager.cpp#l1533), in particular inside some of the PR_Wait calls I see there. It might look as if the `root` monitor is blocked for quite a while? > [Parent 1570, Main Thread] WARNING: ContentParent: id=7fa0638e7c00 - BlockShutdown: NotifyImpendingShutdown.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3635 Again, these are harmless (but too verbose) messages that help us just in debugging, so their existence is normal every single time we shut down a content process.
Bug 1788599 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Mike Cloaked from comment #14) > The 15 seconds shutdown time remains the case with 106.0b1 where the console message is back: From [the profile it seems](https://share.firefox.dev/3RQZpzA) Thunderbird is stuck inside [`nsMsgAccountManager::CleanupOnExit`](https://hg.mozilla.org/comm-central/file/tip/mailnews/base/src/nsMsgAccountManager.cpp#l1533), in particular inside some of the `PR_Wait` calls I see there. It might look as if the `root` monitor is blocked for quite a while? > [Parent 1570, Main Thread] WARNING: ContentParent: id=7fa0638e7c00 - BlockShutdown: NotifyImpendingShutdown.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3635 Again, these are harmless (but too verbose) messages that help us just in debugging, so their existence is normal every single time we shut down a content process.
(In reply to Mike Cloaked from comment #14) > The 15 seconds shutdown time remains the case with 106.0b1 where the console message is back: From [the profile it seems](https://share.firefox.dev/3RQZpzA) Thunderbird is stuck inside [`nsMsgAccountManager::CleanupOnExit`](https://hg.mozilla.org/comm-central/file/tip/mailnews/base/src/nsMsgAccountManager.cpp#l1533), in particular inside some of the `PR_Wait` calls I see there. It might look as if the `root` monitor is blocked for quite a while? Edit: Actually `while (inProgress && loopCount++ < 5000)` might even suggest that `root` is never unblocked but we give just up (numerically 5000*1000 usec would add up to a 5 sec delay only, but I can imagine that the processing in between easily doubles this). Besides investigating what blocks root, this could benefit also from a `SpinEventLoopUntil` and an appropriate timeout, to make the timings more reliable. > [Parent 1570, Main Thread] WARNING: ContentParent: id=7fa0638e7c00 - BlockShutdown: NotifyImpendingShutdown.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3635 Again, these are harmless (but too verbose) messages that help us just in debugging, so their existence is normal every single time we shut down a content process.
(In reply to Mike Cloaked from comment #14) > The 15 seconds shutdown time remains the case with 106.0b1 where the console message is back: From [the profile it seems](https://share.firefox.dev/3RQZpzA) Thunderbird is stuck inside [`nsMsgAccountManager::CleanupOnExit`](https://hg.mozilla.org/comm-central/file/tip/mailnews/base/src/nsMsgAccountManager.cpp#l1533), in particular inside some of the `PR_Wait` calls I see there. It might look as if the `root` monitor is blocked for quite a while? Edit: Actually `while (inProgress && loopCount++ < 5000)` might even suggest that `root` is never unblocked but we give just up (numerically 5000*1000 usec would add up to a 5 sec delay only, but I can imagine that the processing in between easily doubles this). Besides investigating what blocks `root`, this could benefit also from a `SpinEventLoopUntil` and an appropriate timeout, to make the timings more reliable. > [Parent 1570, Main Thread] WARNING: ContentParent: id=7fa0638e7c00 - BlockShutdown: NotifyImpendingShutdown.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3635 Again, these are harmless (but too verbose) messages that help us just in debugging, so their existence is normal every single time we shut down a content process.