cherry-pick(worklets-0.10-stable): time-of-check and time-of-use destructor safety (#9790)#9801
Merged
tjzel merged 1 commit intoJul 1, 2026
Conversation
Base automatically changed from
@tjzel/worklets-0.10-stable/cherry-pick-#9789
to
worklets-0.10-stable
July 1, 2026 09:58
## Summary Currently the way we check if the runtime is alive for safe destructor invocations has a chance to lead to crashes anyway, since the runtime can get cleaned up immediately after the check, since it lacks a locking mechanism. ## Test plan The test example from #9789 works. (cherry picked from commit 71774cb)
tjzel
force-pushed
the
@tjzel/worklets-0.10-stable/cherry-pick-#9790
branch
from
5e9fe7e to
817d5df
Compare
tshmieldev
approved these changes
Jul 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-picking #9790
Requires #9800 to be merged first.