Hm, so that's weird because the Watchdog has a workers-specific crash that produces output different than what's happening in those failures. Specifically, in the [Watchdog](https://searchfox.org/mozilla-central/rev/b2b0077c2e6a516a76bf8077d6f0237c58f5959a/toolkit/components/terminator/nsTerminator.cpp#207)} an explicit call to [RuntimeService::CrashIfHanging](https://searchfox.org/mozilla-central/rev/b2b0077c2e6a516a76bf8077d6f0237c58f5959a/dom/workers/RuntimeService.cpp#1729) which at the top checks whether mDomainMap is empty. If it's empty, it early returns to allow the crash to have the string ["Shutdown too long, probably frozen, causing a crash."](https://searchfox.org/mozilla-central/rev/b2b0077c2e6a516a76bf8077d6f0237c58f5959a/toolkit/components/terminator/nsTerminator.cpp#213) we're seeing here. If it's not empty, the crash will start with ["Workers Hanging"](https://searchfox.org/mozilla-central/rev/b2b0077c2e6a516a76bf8077d6f0237c58f5959a/dom/workers/RuntimeService.cpp#1766) The crashes at https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274151077&repo=try&lineNumber=36610 and https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274154705&repo=try&lineNumber=36743 indeed don't seem to have this signature. Instead the problems seem to be at ~BrowserProcessSubThread in both: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274151077&repo=try&lineNumber=36659 and https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274154705&repo=try&lineNumber=36792 ? Do you have other try failures that more directly implicate this bug?
Bug 1594572 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hm, so that's weird because the Watchdog has a workers-specific crash that produces output different than what's happening in those failures. Specifically, in the [Watchdog](https://searchfox.org/mozilla-central/rev/b2b0077c2e6a516a76bf8077d6f0237c58f5959a/toolkit/components/terminator/nsTerminator.cpp#207) an explicit call to [RuntimeService::CrashIfHanging](https://searchfox.org/mozilla-central/rev/b2b0077c2e6a516a76bf8077d6f0237c58f5959a/dom/workers/RuntimeService.cpp#1729) which at the top checks whether mDomainMap is empty. If it's empty, it early returns to allow the crash to have the string ["Shutdown too long, probably frozen, causing a crash."](https://searchfox.org/mozilla-central/rev/b2b0077c2e6a516a76bf8077d6f0237c58f5959a/toolkit/components/terminator/nsTerminator.cpp#213) we're seeing here. If it's not empty, the crash will start with ["Workers Hanging"](https://searchfox.org/mozilla-central/rev/b2b0077c2e6a516a76bf8077d6f0237c58f5959a/dom/workers/RuntimeService.cpp#1766) The crashes at https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274151077&repo=try&lineNumber=36610 and https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274154705&repo=try&lineNumber=36743 indeed don't seem to have this signature. Instead the problems seem to be at ~BrowserProcessSubThread in both: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274151077&repo=try&lineNumber=36659 and https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=274154705&repo=try&lineNumber=36792 ? Do you have other try failures that more directly implicate this bug?