1772084 - Ensure WorkerThreadPrimaryRunnable will not run any events after the cycle collector is destroyed.

Status: RESOLVED WONTFIX

(Core :: DOM: Workers, task)

Description

[Jens Stutte [:jstutte]]

In bug 1769878 we've seen that WorkerThreadPrimaryRunnable calls ClearMainEventQueue after the CC is destroyed. ClearMainEventQueue potentially does another round of NS_ProcessPendingEvents. If any assumed to be CC'ed object has not yet been destroyed and is referenced by some event such that it gets released during this round, the CC will crash.

We want to avoid that we do any events processing after we destroyed our cycle collector.

Comment 1

[Jens Stutte [:jstutte]]

Attachment: Bug 1772084 - Ensure WorkerThreadPrimaryRunnable will not run any events after the cycle collector is destroyed. r?#dom-worker-reviewers

Comment 2

[Jens Stutte [:jstutte]]

I am not sure I will be able to fix this any time soon. The patch as such is probably to be abandoned, but I leave it here for reference what we tried so far. At least the crashtest will be added already in bug 1769878 (in the right directory).

Comment 3

[Jens Stutte [:jstutte]]

We added some extra processing before and after we destroy the cycle collector in bug 1803540 and we added the test already, so this seems obsolete now.