The JS/TS language service crashed 5 times in the last 5 Minutes.

[ImBIOS]

Just curious, does normally TypeScript's IntelliSense won't work in this codebase? I even reported it to @microsoft:

• The JS/TS language service crashed 5 times in the last 5 Minutes. microsoft/vscode#224067

[ImBIOS]

Found the problem and solution:

Problem

󰀵  󱑍 09:53  ﱮ cal-com    main !?+787 via  v18.20.3   3s 
 ✗  node -e 'console.log(v8.getHeapStatistics().heap_size_limit/(1024*1024))'

2096

󰀵  󱑍 09:53  ﱮ cal-com    main !?+787 via  v18.20.3 
 ➜  yarn tsc --pretty --noEmit packages/core/EventManager.test.ts 

<--- Last few GCs --->

[63836:0x673f8b0]    71923 ms: Scavenge (reduce) 2042.8 (2082.0) -> 2041.9 (2082.2) MB, 7.7 / 0.0 ms  (average mu = 0.138, current mu = 0.007) allocation failure; 
[63836:0x673f8b0]    72849 ms: Mark-sweep (reduce) 2042.9 (2082.2) -> 2041.2 (2082.2) MB, 910.3 / 0.0 ms  (average mu = 0.151, current mu = 0.164) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb9c310 node::Abort() [/home/username/.proto/tools/node/18.20.3/bin/node]
 2: 0xaa27ee  [/home/username/.proto/tools/node/18.20.3/bin/node]
 3: 0xd73eb0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/home/username/.proto/tools/node/18.20.3/bin/node]
 4: 0xd74257 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/home/username/.proto/tools/node/18.20.3/bin/node]
 5: 0xf515d5  [/home/username/.proto/tools/node/18.20.3/bin/node]
 6: 0xf524d8 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/home/username/.proto/tools/node/18.20.3/bin/node]
 7: 0xf629d3  [/home/username/.proto/tools/node/18.20.3/bin/node]
 8: 0xf63848 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/username/.proto/tools/node/18.20.3/bin/node]
 9: 0xf3e19e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/username/.proto/tools/node/18.20.3/bin/node]
10: 0xf3f567 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/username/.proto/tools/node/18.20.3/bin/node]
11: 0xf2076a v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/home/username/.proto/tools/node/18.20.3/bin/node]
12: 0x12e599f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/home/username/.proto/tools/node/18.20.3/bin/node]
13: 0x17125f9  [/home/username/.proto/tools/node/18.20.3/bin/node]

Solution

# Increase nodejs memory limit
export NODE_OPTIONS="--max-old-space-size=4096"

You can place this in your shell config like ~/.zshrc to run each startup.

Reference:

• https://stackoverflow.com/questions/53230823/fatal-error-ineffective-mark-compacts-near-heap-limit-allocation-failed-javas