Skip to content

Fix initialization of NotCloneable VMs. #63

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

Merged
merged 1 commit into from
Oct 9, 2020

Conversation

PiotrSikora
Copy link
Member

@PiotrSikora PiotrSikora commented Oct 2, 2020

Cloned VM doesn't (always) have a copy of the bytecode,
so initialize it using bytecode from the base VM.

Note that we don't have NotCloneable runtime right now.

Signed-off-by: Piotr Sikora piotrsikora@google.com

Signed-off-by: Piotr Sikora <piotrsikora@google.com>
@PiotrSikora PiotrSikora requested a review from jplevyak October 2, 2020 21:35
@kyessenov
Copy link
Collaborator

Can we have a little more comment what the change does?

@PiotrSikora
Copy link
Member Author

Can we have a little more comment what the change does?

Updated commit message, let me know if that's clear enough.

@kyessenov
Copy link
Collaborator

What does the user experience in this case? Does it impact them?

@PiotrSikora
Copy link
Member Author

PiotrSikora commented Oct 2, 2020

What does the user experience in this case? Does it impact them?

VM won't start. As mentioned, we don't have NotClonable runtimes right now, I ran into it when I was debugging the memory leak you pointed out, and switched V8 from CompiledBytecode to NotCloneable to avoid the (de)serialization when passing V8 Isolate between threads.

@PiotrSikora PiotrSikora merged commit 92f02c0 into proxy-wasm:master Oct 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants