[ Nest.js 메모리 누수 ] 내 메모리, 누가 자꾸 훔쳐먹어요

<--- Last few GCs --->

[29505:0x140008000] 42353552 ms: Mark-sweep 4058.3 (4144.0) -> 4044.1 (4144.0) MB, 2650.0 / 0.0 ms  (average mu = 0.642, current mu = 0.011) allocation failure scavenge might not succeed
[29505:0x140008000] 42356151 ms: Mark-sweep 4059.9 (4144.0) -> 4045.8 (4144.7) MB, 2571.7 / 0.0 ms  (average mu = 0.476, current mu = 0.010) allocation failure scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0x10434d8d8 node::Abort() [/usr/local/bin/node]
 2: 0x10434da60 node::ModifyCodeGenerationFromStrings(v8::Local<v8::Context>, v8::Local<v8::Value>, bool) [/usr/local/bin/node]
 3: 0x10448f36c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 4: 0x10448f300 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 5: 0x10461281c v8::internal::Heap::GarbageCollectionReasonToString(v8::internal::GarbageCollectionReason) [/usr/local/bin/node]
 6: 0x10461133c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
 7: 0x10461c684 v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
 8: 0x10461c718 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
 9: 0x1045ef5ac v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/local/bin/node]
10: 0x1049276d0 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/local/bin/node]
11: 0x104c3ab8c Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/usr/local/bin/node]
12: 0x109391d54 
13: 0x104c56fe8 Builtins_ArrayMap [/usr/local/bin/node]
14: 0x104bce818 Builtins_InterpreterEntryTrampoline [/usr/local/bin/node]
15: 0x104bce818 Builtins_InterpreterEntryTrampoline [/usr/local/bin/node]
16: 0x104bce818 Builtins_InterpreterEntryTrampoline [/usr/local/bin/node]
17: 0x104bce818 Builtins_InterpreterEntryTrampoline [/usr/local/bin/node]
18: 0x104bce818 Builtins_InterpreterEntryTrampoline [/usr/local/bin/node]
19: 0x104bfde14 Builtins_AsyncFunctionAwaitResolveClosure [/usr/local/bin/node]
20: 0x104c82c78 Builtins_PromiseFulfillReactionJob [/usr/local/bin/node]

 

신나게 회사에서 일하다가 현재 켜져있는 크롤링 서버를 그대로 두고 퇴근했다.

갔다와서보니 위와 같은 메세지가 나를 반겼다... 아침부터 나에게 이런 시련을,,,

 

이런 경우는 처음이라 구글링을 해보니 메모리 누수라고 한다.

 

해당 메시지 바로 직전에 디버깅 용으로 켜둔 쿼리 디버깅을 확인해보니 새벽에 돌아가는 배치서비스가 문제였다.

눈물을 머금고 해결해보겠다.

 

우선 디버깅부터 들어가보자.

 

 

launch.json

 

디버깅용 launch.json 을 생성한다.