[wasm] crypto deadlock fix
- more locking before manipulation with the channel state.
- more asserts about expected states
- removed extra console.debug logging
- renamed wait method to make it clearer what we are waiting for
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
Issue Details
- more locking before manipulation with the channel state.
- more asserts about expected states
- removed extra console.debug logging
- renamed wait method to make it clearer what we are waiting for
| Author: | pavelsavara |
|---|---|
| Assignees: | pavelsavara |
| Labels: |
|
| Milestone: | 7.0.0 |
CI test with multiple workitems on Helix is https://github.com/dotnet/runtime/pull/73629
re:having-spin-or-nonblocking-in-fn-name, I added those to make it obvious to spot cases where they might get used in incorrect contexts. For example, using a spin wait for a state inside a lock, which could cause a deadlock because the other side is waiting for that lock, so it can change the state.
/azp run runtime-wasm
Azure Pipelines successfully started running 1 pipeline(s).