https://crash-stats.mozilla.com/report/index/b702d8a5-2331-4f6e-bc9e-5e84c0180206#allthreads here QuotaManager receives the xpcom-shutdown notification and it blocks the main-thread. workerinternals::RuntimeService doesn't receive the same notification and after a timeout, it crashes. https://crash-stats.mozilla.com/report/index/27c652d6-9da8-40c0-ad21-dc3c60180206#allthreads here a similar issue.

Note that, soon, worker shutdown should start when xpcom-will-shutdown is received, but the current QM code, can block other component shutdown as well.

https://crash-stats.mozilla.com/report/index/9d01210c-783d-4805-87d9-6c4ed0180206#allthreads https://crash-stats.mozilla.com/report/index/8907d29a-a667-4b34-80ee-e19d20180206#allthreads The signature is changed. Here some new crash reports with the new workerinternals::RuntimeService signature.

https://crash-stats.mozilla.com/report/index/9d01210c-783d-4805-87d9-6c4ed0180206#allthreads is blocked by Quota's Manager::ShutdownAll() in thread 16. This is going to wait for existing contexts/IO operations to Cancel and complete. I suppose it's possible for those to take a while (profile on a network?), though it's unclear how long before the Worker timeout causes a forced crash.

"perf" key word?

Andrea, how different is bug 1411908 from this one? Maybe duping this one?

Yes, it is.