Vitest crashes without showing the test name which is causing the issue

[dhavall08]

I am getting the following error after some file changes and adding new files. However, there are no changes to test files but vitest fails with the following message without any clue what to debug next. The order of files is random so it's impossible to see if it's any file causing issues or something else. Also, it says JavaScript heap out of memory but it doesn't seem to be a memory issue as I tried adding more memory to poolOptions.vmThreads.memoryLimit in vite.config.js and also tried with max-old-space-size with Node command. I also tried with --logHeapUsage flag but haven't got any specific issue for the test. It would be helpful If someone could provide any insight into what could be the issue or a easier way to debug this kind of issue.

Version: "vitest": "^1.4.0",
Environment: jsdom.
along with React Testing Library.

# <a lot of passed test names but not the pending or in progress one>

<--- Last few GCs --->

[166426:0x7febf8000d60]   164436 ms: Mark-sweep (reduce) 1287.4 (1639.0) -> 1287.4 (1589.3) MB, 458.1 / 0.0 ms  (average mu = 0.044, current mu = 0.037) last resort; GC in old space requested
[166426:0x7febf8000d60]   164916 ms: Mark-sweep (reduce) 1287.4 (1589.3) -> 1287.4 (1571.5) MB, 480.5 / 0.0 ms  (average mu = 0.022, current mu = 0.000) last resort; GC in old space requested


<--- JS stacktrace --->

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: 0xb83f50 node::Abort() [node (vitest)]
 2: 0xa94834  [node (vitest)]
 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node (vitest)]
 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node (vitest)]
 5: 0xf3039f v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node (vitest)]
 6: 0xf10338 v8::internal::Factory::CodeBuilder::AllocateCode(bool) [node (vitest)]
 7: 0xf2427c v8::internal::Factory::CodeBuilder::BuildInternal(bool) [node (vitest)]
 8: 0xf24d1e v8::internal::Factory::CodeBuilder::Build() [node (vitest)]
 9: 0x15de69e v8::internal::RegExpMacroAssemblerX64::GetCode(v8::internal::Handle<v8::internal::String>) [node (vitest)]
10: 0x12a3186 v8::internal::RegExpCompiler::Assemble(v8::internal::Isolate*, v8::internal::RegExpMacroAssembler*, v8::internal::RegExpNode*, int, v8::internal::Handle<v8::internal::String>) [node (vitest)]
11: 0x12c30c7 v8::internal::RegExpImpl::Compile(v8::internal::Isolate*, v8::internal::Zone*, v8::internal::RegExpCompileData*, v8::base::Flags<v8::internal::RegExpFlag, int>, v8::internal::Handle<v8::internal::String>, v8::internal::Handle<v8::internal::String>, bool, unsigned int&) [node (vitest)]
12: 0x12c3842 v8::internal::RegExpImpl::CompileIrregexp(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, bool) [node (vitest)]
13: 0x12c43fe v8::internal::RegExpImpl::IrregexpPrepare(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>) [node (vitest)]
14: 0x12c45a3 v8::internal::RegExpImpl::IrregexpExec(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, int, v8::internal::Handle<v8::internal::RegExpMatchInfo>, v8::internal::RegExp::ExecQuirks) [node (vitest)]
15: 0x12e993e v8::internal::Runtime_RegExpExec(int, unsigned long*, v8::internal::Isolate*) [node (vitest)]
16: 0x17035b9  [node (vitest)]
Aborted (core dumped)

[hi-ogawa]

That's a "normal" log of nodejs out of memory error, so it's likely that your code has something to do with hogging memory.

Your log indicates memory limit is around 1287.4 (1589.3) MB, so it looks like it's a default limit. Can you explain what you did with max-old-space-size?

[dhavall08]

Thanks for the reply. I tried these alternate commands to provide more memory.

1. When I run tests with node --max-old-space-size=8192 `which npm` t, then I get the following lines:

<--- Last few GCs --->

[13752:0x7fd394000d60]   229361 ms: Mark-sweep (reduce) 1309.4 (1689.7) -> 1309.4 (1638.4) MB, 437.5 / 0.0 ms  (average mu = 0.036, current mu = 0.035) last resort; GC in old space requested
[13752:0x7fd394000d60]   229848 ms: Mark-sweep (reduce) 1309.4 (1638.4) -> 1309.4 (1619.9) MB, 486.2 / 0.0 ms  (average mu = 0.017, current mu = 0.000) last resort; GC in old space requested


<--- JS stacktrace --->

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: 0xb83f50 node::Abort() [node (vitest)]
 2: 0xa94834  [node (vitest)]
 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node (vitest)]
 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node (vitest)]
...

2. If I run with export NODE_OPTIONS="--max-old-space-size=12288" && npm run test:

<--- Last few GCs --->

[18940:0x7f3f7c000d60]   195567 ms: Mark-sweep (reduce) 1345.1 (1725.8) -> 1345.1 (1676.3) MB, 459.9 / 0.0 ms  (average mu = 0.070, current mu = 0.034) last resort; GC in old space requested
[18940:0x7f3f7c000d60]   196081 ms: Mark-sweep (reduce) 1345.1 (1676.3) -> 1345.0 (1658.1) MB, 513.9 / 0.0 ms  (average mu = 0.034, current mu = 0.000) last resort; GC in old space requested


<--- JS stacktrace --->

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: 0xb83f50 node::Abort() [node (vitest)]
 2: 0xa94834  [node (vitest)]
 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node (vitest)]
 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node (vitest)]
...

3. Just tried with other alternative to check if it was correctly passed npm run test --node-flags --max-old-space-size=8192

<--- Last few GCs --->

[21945:0x7f0fd0000d60]   209191 ms: Mark-sweep (reduce) 1347.0 (1714.9) -> 1345.9 (1665.1) MB, 524.7 / 0.0 ms  (average mu = 0.160, current mu = 0.030) last resort; GC in old space requested
[21945:0x7f0fd0000d60]   209767 ms: Mark-sweep (reduce) 1345.9 (1665.1) -> 1345.8 (1647.9) MB, 576.1 / 0.0 ms  (average mu = 0.081, current mu = 0.000) last resort; GC in old space requested


<--- JS stacktrace --->

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: 0xb83f50 node::Abort() [node (vitest)]
 2: 0xa94834  [node (vitest)]
...

[hi-ogawa]

I'm not sure since It's a long time ago when I saw this last time, but I thought ... MB should roughly change as you change --max-old-space-size (assuming your PC actually has more memory), so maybe the node option is not working? I don't think I can help this further unless you have a reproduction.

[dhavall08]

Thanks for your time checking it. When I tried rebasing onto my latest changes today, it got fixed magically.