During the CI process, the memory of my vitest will explode

Describe the bug

During the CI process, the memory of my vitest will explode

Reproduction

• cd apps/promotion
• rushx test Found configuration in /home/code/rush.json Rush Multi-Project Build Tool 5.71.0 - Node.js 14.18.1 (LTS)

“vitest run” RUN v0.18.0 /home/code/apps/promotion events.js:377 throw er; // Unhandled ‘error’ event ^ RangeError [Error]: WebAssembly.instantiate(): Out of memory: wasm memory at internal/deps/cjs-module-lexer/dist/lexer.js:1:33593 Emitted ‘error’ event on process instance at: at emitUnhandledRejectionOrErr (internal/event_target.js:579:11) at MessagePort.[nodejs.internal.kHybridDispatch] (internal/event_target.js:403:9) at MessagePort.exports.emitMessage (internal/per_context/messageport.js:18:26) The script failed with exit code 1

System Info

System:
    OS: Linux 5.4 Debian GNU/Linux 10 (buster) 10 (buster)
    CPU: (104) x64 Intel(R) Xeon(R) Platinum 8269CA CPU @ 2.50GHz
    Memory: 29.09 GB / 32.00 GB
    Container: Yes
    Shell: 5.0.3 
  Binaries:
    Node: 14.18.1 
    Yarn: 1.22.15 
    npm: 6.14.15

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[alexlafroscia]

We’re seeing this error sporadically in our own CI process, and setting the --max-old-space-size alone didn’t fix things for us

[frankwallis]

I’m seeing the same thing. It’s interesting that it only happens in CI - I wonder if vitest is trying to utilise all the available cores on the physical node when calculating the number of threads to allocate.