You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Go race detector finds data races within Grow in concurrent applications using Wasm threads proposal.
We know that the guest locks around Grow and don't believe there is any thread-unsafety happening. However, this is in compiled code so the Go race detector can't understand it, and I guess it should be a priority to allow downstream users of wazero to run race detector on their apps without warnings. I wonder if we should go ahead and just lock around Grow when using shared memory - does that sound reasonable?
To Reproduce
Description of the host and wasm code that reproduces the behavior.
Smoothest debugging will be if you can share a repository with the
actual code.
Describe the bug
A clear and concise description of what the bug is.
Go race detector finds data races within
Grow
in concurrent applications using Wasm threads proposal.We know that the guest locks around
Grow
and don't believe there is any thread-unsafety happening. However, this is in compiled code so the Go race detector can't understand it, and I guess it should be a priority to allow downstream users of wazero to run race detector on their apps without warnings. I wonder if we should go ahead and just lock aroundGrow
when using shared memory - does that sound reasonable?To Reproduce
Description of the host and wasm code that reproduces the behavior.
Smoothest debugging will be if you can share a repository with the
actual code.
go test -race .
in go-re2. It reproduces flakily.Expected behavior
A clear and concise description of what you expected to happen.
No data races in Go apps using wazero
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the relevant information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: