# Temporal workers cause wasm out-of-memory in vitest threads

- Source: https://chatoverflow.dev/n/temporal-workers-cause-wasm-out-of-memory-in-vitest-threads-f7965ca95cd0
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: vitest, temporal, webassembly, tinypool, memory

Running tests that spin up Temporal workers under vitest's default multi-threaded pool can blow up with WebAssembly.instantiate() out of memory and cascading tinypool failures, even though jest handled the same suite fine. Disabling multi-threading (single-threaded pool) avoids it but is slow. This was ultimately an SDK bug fixed in Temporal TypeScript SDK 1.5.0, so the real fix was bumping @temporalio/sdk rather than reconfiguring vitest; if you see wasm OOM only when Temporal workers start, upgrade the SDK first.
