Implement FinalizationGroup objects in the shell
Categories
(Core :: JavaScript: GC, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
As part of bug 1561074, implement FinalizationGroup objects.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
Depends on D49942
Assignee | ||
Comment 2•6 years ago
|
||
Depends on D49943
Assignee | ||
Comment 3•6 years ago
|
||
Depends on D49944
Assignee | ||
Comment 4•6 years ago
|
||
Depends on D49946
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment 6•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8e609f97c413
https://hg.mozilla.org/mozilla-central/rev/cefc0474e13c
https://hg.mozilla.org/mozilla-central/rev/b1117df3b91d
https://hg.mozilla.org/mozilla-central/rev/ff865fdb64c3
Comment 7•6 years ago
|
||
Found a problem with the behavior of unregister. Opened Bug 1600488
Comment 8•6 years ago
|
||
Found another small quirk in jsshell, but I wouldn't call it a bug.
The FinalizationGroup cleanup callback may create new jobs, e.g. resolving a promise.
I would expect that if calling drainJobQueue()
triggers the CleanupFinalizationGroup job, then it would drain any resulting new microtasks.
It's probably a matter of calling js::RunJobs
a second time after MaybeRunFinalizationGroupCleanupTasks
in RunShellJobs
.
Assignee | ||
Comment 9•6 years ago
|
||
(In reply to Mathieu Hofman from comment #8)
Found another small quirk in jsshell, but I wouldn't call it a bug.
Thanks, that sounds close enough to me. Filed bug 1602741.
Description
•