Live snapshots 8: detach live wrappables and reset their handles - #7143
Open
dbezhetskov wants to merge 7 commits into
Open
Live snapshots 8: detach live wrappables and reset their handles#7143dbezhetskov wants to merge 7 commits into
dbezhetskov wants to merge 7 commits into
Conversation
Build a throwaway “zygote” Worker from the same source and bindings,
solely to evaluate top-level code and produce a snapshot artifact.
The SnapshotArtifact encapsulates all the data required to construct
a new isolate from a V8 startup snapshot.
Add a SnapshotConfig parameter to WorkerdApi controlling how the
isolate is created:
- kj::none: a regular isolate, no snapshots involved
- MutableSnapshot: the isolate is created via v8::SnapshotCreator
and fills the snapshot artifact
- ReadonlySharedSnapshot: the isolate boots from a previously
produced snapshot blob
To create snapshot we need to reset all C++ handles first. Here we reset IsolateBase level handles.
Instead of creating impl->env, impl->ctxExports, and the exported
handler table only to reset them again before CreateBlob, don't create
them at all in the zygote. This is safe: top-level code has already
executed by this point, and the zygote worker never handles requests,
so nothing reads this state.
No JavaScript values are lost to garbage collection either, because the
values these handles would refer to are already retained elsewhere:
impl->env == IsolateBase::workerEnvObj
impl->ctxExports == IsolateBase::workerExportsObj
A real Worker repopulates these handles in START_FROM_SNAPSHOT mode.
Reset the memoized andcontext constructor-templates kept per JSG_RESOURCE type by the TypeWrapper machinery.
Add visitStructTypeHandles to traverse all struct types and reset their template and field handles.
Reset the per-entry module / source-object / mutable-exports / synthetic handles of every instantiated ModuleInfo.
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
1 participant
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.
depends on: #7142