fix[testVueSdk]: try to not use a global isolate instance and create fresh instance for each request #4210
+82
−82
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.
Description
The Strategy:
This guarantees memory cleanup because the entire memory block is freed by C++.
Screenshot
If relevant, add a screenshot or two of the changes you made.
Note
Switches Node evaluate runtime to create and dispose a fresh
isolated-vmper request, removing the global context and allowing configurable isolate options.packages/sdks/src/functions/evaluate/node-runtime/node-runtime.ts):ivm.Isolateper call inrunInNodeand dispose it infinally.Context/singleton isolate management (setIsolateContext/getIsolateContext).setIvmto accept optionalIsolateOptionsand store them inIVM_OPTIONSfor per-request use.log,BUILDER_IVM) insiderunInNode; keep state propagation viaBUILDER_SET_STATEand argument proxying unchanged.Written by Cursor Bugbot for commit 6c588e5. This will update automatically on new commits. Configure here.