Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mechanism for tracing wrappers with GCProtected set #225

Merged
merged 1 commit into from
Aug 24, 2023

Conversation

caitp
Copy link
Collaborator

@caitp caitp commented Aug 14, 2023

Assuming all GCProtected wrappers are tracked within Caches, this should ensure that their JS object and the cppgc wrapper itself are not collected (or are at least continued to be traced), until the bit is released.

This is done by allocating a dummy object and storing it on the global object of a runtime, which when traced, performs a trace of every object known to its local Caches instance.

Assuming all GCProtected wrappers are tracked within Caches, this should ensure that
their JS object and the cppgc wrapper itself are not collected (or are at least continued
to be traced), until the bit is released.

This is done by allocating a dummy object and storing it on the global object of a runtime,
which when traced, performs a trace of every object known to its local Caches instance.
@cla-bot cla-bot bot added the cla: yes label Aug 14, 2023
@NathanWalker NathanWalker changed the base branch from dev to v8-v11 August 24, 2023 15:53
@NathanWalker NathanWalker merged commit 0b7ee2d into NativeScript:v8-v11 Aug 24, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants