mirrors/ladybird
0
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-06-26 04:02:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

LibJS+LibGC: Run FinalizationRegistry cleanup host hook *after* GC

Browse source 
Before this change, it was possible for a second GC to get triggered
in the middle of a first GC, due to allocations happening in the
FinalizationRegistry cleanup host hook. To avoid this causing problems,
we add a "post-GC task" mechanism and use that to invoke the host hook
once all other GC activity is finished, and we've unset the "collecting
garbage" flag.

Note that the test included here only fails reliably when running with
the -g flag (collect garbage after each allocation).

Fixes #3051
This commit is contained in:
Andreas Kling 2025-01-23 09:59:22 +01:00 • committed by Andreas Kling
parent b7a554d1f2
commit 51a91771b8
Notes: github-actions[bot] 2025-01-23 11:11:21 +00:00
4 changed files with 55 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

9
Libraries/LibJS/Runtime/FinalizationRegistry.cpp
View file

@ -57,8 +57,13 @@ void FinalizationRegistry::remove_dead_cells(Badge<GC::Heap>)
any_cells_were_removed = true;
break;
}
if (any_cells_were_removed)
vm().host_enqueue_finalization_registry_cleanup_job(*this);
if (any_cells_were_removed) {
// NOTE: We make a GC::Root here to ensure that the FinalizationRegistry stays alive
// even if a subsequent GC is triggered before the callback has a chance to run.
heap().enqueue_post_gc_task([that = GC::make_root(this)]() {
that->vm().host_enqueue_finalization_registry_cleanup_job(*that);
});
}
}
// 9.13 CleanupFinalizationRegistry ( finalizationRegistry ), https://tc39.es/ecma262/#sec-cleanup-finalization-registry