-
Notifications
You must be signed in to change notification settings - Fork 163
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
Using wasmer from goroutines #84
Comments
Since wasmerio/wasmer#807, I would say it is safe to use |
Some precisions: |
https://golang.org/pkg/runtime/#LockOSThread can be useful for reentrance. |
Thanks a lot! Can I re-conclude a bit?
Correct? |
|
Ok, https://golang.org/pkg/runtime/#LockOSThread does the job, thank you very much! |
#84 (comment) isn't true. I didn't know that goroutines can run on a same thread or can be moved to another thread. |
Summary
What is the safe way to use wasmer from multiple goroutines?
Additional details
If
instance
(result ofwasm.NewInstance
) is used by only one goroutine at any time - is it enough? The potential problem is that one goroutine might be executed by few threads.The text was updated successfully, but these errors were encountered: