Fix bug where the WasmWorker instance is disposed but never re-spawned on page reloads + writeMemory when WASM memory is SharedArrayBuffer #2211
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.
The
WasmWorkerFactory
instance caches a singleIWasmWorker
instance but thedispose
method on theIWasmWorker
instance still terminates the underlying worker. The effect is that the worker in the@vscode/dwarf-debugging
terminates on browser page reloads and never re-spawns again until debugging is restarted.This PR addresses this issue by still caching a single
IWasmWorker
instance but re-spawning it if the previous call todispose
caused the "ref count" to reach zero.Possible related to microsoft/vscode-dwarf-debugging#6
Also fixes
writeMemory
when WASM memory isSharedArrayBuffer
.