Out of Heap Space

[suyashkumar]

<--- Last few GCs --->

921367661 ms: Mark-sweep 1376.6 (1435.6) -> 1376.6 (1435.6) MB, 1414.5 / 0.0 ms [allocation failure] [GC in old space requested].
921369066 ms: Mark-sweep 1376.6 (1435.6) -> 1376.6 (1435.6) MB, 1404.9 / 0.0 ms [allocation failure] [GC in old space requested].
921370478 ms: Mark-sweep 1376.6 (1435.6) -> 1376.6 (1409.6) MB, 1392.8 / 0.0 ms [last resort gc].
921371903 ms: Mark-sweep 1376.6 (1409.6) -> 1376.6 (1409.6) MB, 1425.1 / 0.0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x7ad13ccfb39 <JS Object>
    1: hook [/home/bitnami/ADPL/software/cloud-dashboard/node-server/node_modules/hooks-fixed/hooks.js:~9] [pc=0x33a8c86eb522] (this=0x2fa854de8f61 <a model with map 0x3571efce9d9>,name=0x2fa854de9e09 <String[18]: $__original_remove>,fn=0x389919149b31 <JS Function remove (SharedFunctionInfo 0x389919144a09)>,errorCb=0x7ad13c04381 <undefined>)
    2: $pre(aka pre) [/home/bitnami/ADPL/software/clou...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0x10c9ffc [node]
 3: v8::Utils::ReportApiFailure(char const*, char const*) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
 5: v8::internal::Handle<v8::internal::JSFunction> v8::internal::Factory::New<v8::internal::JSFunction>(v8::internal::Handle<v8::internal::Map>, v8::internal::AllocationSpace) [node]
 6: v8::internal::Factory::NewFunction(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::SharedFunctionInfo>, v8::internal::Handle<v8::internal::Context>, v8::internal::PretenureFlag) [node]
 7: v8::internal::Factory::NewFunctionFromSharedFunctionInfo(v8::internal::Handle<v8::internal::SharedFunctionInfo>, v8::internal::Handle<v8::internal::Context>, v8::internal::PretenureFlag) [node]
 8: v8::internal::Runtime_NewClosure_Tenured(int, v8::internal::Object**, v8::internal::Isolate*) [node]
 9: 0x33a8c20092a7

Seen for the first time today! We may want to upgrade outdated dependencies that may have memory leaks, and looks around to see if there's anything on our end that may be causing this. This doesn't seem to be repeatable and may be transient because this is the first time we've seen this (and the server hasn't been running continuously for that long).

[suyashkumar]

May also be another reason to rewrite backend infra to Golang :)

[mlp6]

Oh my...

[mlp6]

@suyashkumar have we seen this happen again since last summer?