strange heap out of memory nodejsWhat and where are the stack and heap?How can I update NodeJS and NPM to the next versions?Creating a memory leak with JavaHow to fix JavaScript heap out of memory error when importing data to mongodb?Angular 2 AOT build error - JavaScript heap out of memorywebpack exception Allocation failed - JavaScript heap out of memoryFATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory in NodeJSNodeJS - Upload a file causes JavaScript heap out of memoryAWS Lambda - Nodejs: Allocation failed - JavaScript heap out of memoryArtillery JavaScript heap out of memory
A social experiment. What is the worst that can happen?
Would it be legal for a US State to ban exports of a natural resource?
Is it possible to use .desktop files to open local pdf files on specific pages with a browser?
We have a love-hate relationship
Indicating multiple different modes of speech (fantasy language or telepathy)
How can Trident be so inexpensive? Will it orbit Triton or just do a (slow) flyby?
Melting point of aspirin, contradicting sources
Query about absorption line spectra
Proof of Lemma: Every nonzero integer can be written as a product of primes
Should I stop contributing to retirement accounts?
Translation of Scottish 16th century church stained glass
Is a model fitted to data or is data fitted to a model?
Can I use my Chinese passport to enter China after I acquired another citizenship?
Have I saved too much for retirement so far?
Is it improper etiquette to ask your opponent what his/her rating is before the game?
How will losing mobility of one hand affect my career as a programmer?
API Access HTML/Javascript
Is there a word to describe the feeling of being transfixed out of horror?
Java - What do constructor type arguments mean when placed *before* the type?
Should I install hardwood flooring or cabinets first?
Transformation of random variables and joint distributions
Do Legal Documents Require Signing In Standard Pen Colors?
Proving a function is onto where f(x)=|x|.
Divine apple island
strange heap out of memory nodejs
What and where are the stack and heap?How can I update NodeJS and NPM to the next versions?Creating a memory leak with JavaHow to fix JavaScript heap out of memory error when importing data to mongodb?Angular 2 AOT build error - JavaScript heap out of memorywebpack exception Allocation failed - JavaScript heap out of memoryFATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory in NodeJSNodeJS - Upload a file causes JavaScript heap out of memoryAWS Lambda - Nodejs: Allocation failed - JavaScript heap out of memoryArtillery JavaScript heap out of memory
0
My node server is getting heap out of memory now n then. I tried so hard to debug but problem is still same.
I am getting this error
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
4|app | 1: node::Abort() [node /home/app/server.js]
4|app | 2: 0x1356bec [node /home/app/server.js]
4|app | 3: v8::Utils::ReportOOMFailure(char const*, bool) [node /home/app/server.js]
4|app | 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node /home/app/server.js]
4|app | 5: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [node /home/app/server.js]
4|app | 6: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Allocate(v8::internal::Isolate*, int, v8::internal::PretenureFlag) [node /home/app/server.js]
4|app | 7: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Rehash(v8::internal::Handle<v8::internal::OrderedHashSet>, int) [node /home/app/server.js]
4|app | 8: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::EnsureGrowable(v8::internal::Handle<v8::internal::OrderedHashSet>) [node /home/app/server.js]
4|app | 9: v8::internal::Runtime_SetGrow(int, v8::internal::Object**, v8::internal::Isolate*) [node /home/app/server.js]
4|app | 10: 0x7a8879046fd
also sometimes this error
4|app | <--- Last few GCs --->
4|app |
4|app | [11385:0x2b893d0] 764692 ms: Mark-sweep 1398.5 (1871.3) -> 1398.5 (1871.3) MB, 27920.5 / 2.1 ms allocation failure GC in old space requested
4|app | [11385:0x2b893d0] 789281 ms: Mark-sweep 1398.5 (1871.3) -> 1398.3 (1797.3) MB, 24586.0 / 4.6 ms last resort
4|app | [11385:0x2b893d0] 797403 ms: Mark-sweep 1398.3 (1797.3) -> 1398.3 (1758.8) MB, 8119.9 / 1.0 ms last resort
4|app |
4|app |
4|app | <--- JS stacktrace --->
4|app |
4|app | ==== JS stack trace =========================================
4|app |
4|app | Security context: 0x7e7bf028799 <JSObject>
4|app | 1: add [native collection.js:~111] [pc=0x7a887d1b539](this=0x13ebc6615671 <Set map = 0x18534a9053d9>,p=0x1d9c6aee7719 <String[24]: 5b9827afc5635e2a08f49b6f>)
4|app | 2: baseUniq [/home/app/node_modules/waterline/node_modules/lodash/index.js:~2670] [pc=0x7a887d4d51a](this=0x243308d07421 <JSGlobal Object>,array=0x13ebc66154d9 <JSArray[469241]>,iteratee=0x13ebc6615531 <JSFunction (sfi = 0x3fc29...
Please help me find which code is blowing up the heap. I tried tools to find out leaks but it only tells memory is leaked not where.
node.js memory-leaks heap
asked Mar 21 at 13:43
Shahid KamalShahid Kamal
5510
add a comment |
0
My node server is getting heap out of memory now n then. I tried so hard to debug but problem is still same.
I am getting this error
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
4|app | 1: node::Abort() [node /home/app/server.js]
4|app | 2: 0x1356bec [node /home/app/server.js]
4|app | 3: v8::Utils::ReportOOMFailure(char const*, bool) [node /home/app/server.js]
4|app | 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node /home/app/server.js]
4|app | 5: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [node /home/app/server.js]
4|app | 6: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Allocate(v8::internal::Isolate*, int, v8::internal::PretenureFlag) [node /home/app/server.js]
4|app | 7: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Rehash(v8::internal::Handle<v8::internal::OrderedHashSet>, int) [node /home/app/server.js]
4|app | 8: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::EnsureGrowable(v8::internal::Handle<v8::internal::OrderedHashSet>) [node /home/app/server.js]
4|app | 9: v8::internal::Runtime_SetGrow(int, v8::internal::Object**, v8::internal::Isolate*) [node /home/app/server.js]
4|app | 10: 0x7a8879046fd
also sometimes this error
4|app | <--- Last few GCs --->
4|app |
4|app | [11385:0x2b893d0] 764692 ms: Mark-sweep 1398.5 (1871.3) -> 1398.5 (1871.3) MB, 27920.5 / 2.1 ms allocation failure GC in old space requested
4|app | [11385:0x2b893d0] 789281 ms: Mark-sweep 1398.5 (1871.3) -> 1398.3 (1797.3) MB, 24586.0 / 4.6 ms last resort
4|app | [11385:0x2b893d0] 797403 ms: Mark-sweep 1398.3 (1797.3) -> 1398.3 (1758.8) MB, 8119.9 / 1.0 ms last resort
4|app |
4|app |
4|app | <--- JS stacktrace --->
4|app |
4|app | ==== JS stack trace =========================================
4|app |
4|app | Security context: 0x7e7bf028799 <JSObject>
4|app | 1: add [native collection.js:~111] [pc=0x7a887d1b539](this=0x13ebc6615671 <Set map = 0x18534a9053d9>,p=0x1d9c6aee7719 <String[24]: 5b9827afc5635e2a08f49b6f>)
4|app | 2: baseUniq [/home/app/node_modules/waterline/node_modules/lodash/index.js:~2670] [pc=0x7a887d4d51a](this=0x243308d07421 <JSGlobal Object>,array=0x13ebc66154d9 <JSArray[469241]>,iteratee=0x13ebc6615531 <JSFunction (sfi = 0x3fc29...
Please help me find which code is blowing up the heap. I tried tools to find out leaks but it only tells memory is leaked not where.
node.js memory-leaks heap
asked Mar 21 at 13:43
Shahid KamalShahid Kamal
5510
Are you sure it's a memory leak? i.e. you could first try to increase the max-heap size and see if the error still happens. If yes, maybe check this link which helped me a lot when I had the same problem -> blog.risingstack.com/case-study-node-js-memory-leak-in-ghost
– eol
Mar 21 at 14:11
Thanks I will update after increasing heap size
– Shahid Kamal
Mar 21 at 14:17
As @eol said, try running node --max-old-space-size=8192 <your-entrypoint>.js. We can't really figure out where the leak happens from error you are getting.
– Branko Zivanovic
Mar 21 at 14:18
I got some idea where leak is happening it's a third party library (waterline.js) to query the db. Still testing things. What does old-space means in v8 land? @BrankoZivanovic
– Shahid Kamal
2 days ago
By default, your nodejs process can take 512MB maximum, and when you exceed it's going to crash, just like it did. You can use node --max-old-space-size=2048 index.js to increase it to 2gb or higher, and see if it crashes then, or you may not even be able to profile CPU usage without it if you can't even start a script properly. Good luck!
– Branko Zivanovic
2 days ago
add a comment |
0
0
0
My node server is getting heap out of memory now n then. I tried so hard to debug but problem is still same.
I am getting this error
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
4|app | 1: node::Abort() [node /home/app/server.js]
4|app | 2: 0x1356bec [node /home/app/server.js]
4|app | 3: v8::Utils::ReportOOMFailure(char const*, bool) [node /home/app/server.js]
4|app | 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node /home/app/server.js]
4|app | 5: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [node /home/app/server.js]
4|app | 6: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Allocate(v8::internal::Isolate*, int, v8::internal::PretenureFlag) [node /home/app/server.js]
4|app | 7: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Rehash(v8::internal::Handle<v8::internal::OrderedHashSet>, int) [node /home/app/server.js]
4|app | 8: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::EnsureGrowable(v8::internal::Handle<v8::internal::OrderedHashSet>) [node /home/app/server.js]
4|app | 9: v8::internal::Runtime_SetGrow(int, v8::internal::Object**, v8::internal::Isolate*) [node /home/app/server.js]
4|app | 10: 0x7a8879046fd
also sometimes this error
4|app | <--- Last few GCs --->
4|app |
4|app | [11385:0x2b893d0] 764692 ms: Mark-sweep 1398.5 (1871.3) -> 1398.5 (1871.3) MB, 27920.5 / 2.1 ms allocation failure GC in old space requested
4|app | [11385:0x2b893d0] 789281 ms: Mark-sweep 1398.5 (1871.3) -> 1398.3 (1797.3) MB, 24586.0 / 4.6 ms last resort
4|app | [11385:0x2b893d0] 797403 ms: Mark-sweep 1398.3 (1797.3) -> 1398.3 (1758.8) MB, 8119.9 / 1.0 ms last resort
4|app |
4|app |
4|app | <--- JS stacktrace --->
4|app |
4|app | ==== JS stack trace =========================================
4|app |
4|app | Security context: 0x7e7bf028799 <JSObject>
4|app | 1: add [native collection.js:~111] [pc=0x7a887d1b539](this=0x13ebc6615671 <Set map = 0x18534a9053d9>,p=0x1d9c6aee7719 <String[24]: 5b9827afc5635e2a08f49b6f>)
4|app | 2: baseUniq [/home/app/node_modules/waterline/node_modules/lodash/index.js:~2670] [pc=0x7a887d4d51a](this=0x243308d07421 <JSGlobal Object>,array=0x13ebc66154d9 <JSArray[469241]>,iteratee=0x13ebc6615531 <JSFunction (sfi = 0x3fc29...
Please help me find which code is blowing up the heap. I tried tools to find out leaks but it only tells memory is leaked not where.
node.js memory-leaks heap
asked Mar 21 at 13:43
Shahid KamalShahid Kamal
5510
My node server is getting heap out of memory now n then. I tried so hard to debug but problem is still same.
I am getting this error
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
4|app | 1: node::Abort() [node /home/app/server.js]
4|app | 2: 0x1356bec [node /home/app/server.js]
4|app | 3: v8::Utils::ReportOOMFailure(char const*, bool) [node /home/app/server.js]
4|app | 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node /home/app/server.js]
4|app | 5: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [node /home/app/server.js]
4|app | 6: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Allocate(v8::internal::Isolate*, int, v8::internal::PretenureFlag) [node /home/app/server.js]
4|app | 7: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Rehash(v8::internal::Handle<v8::internal::OrderedHashSet>, int) [node /home/app/server.js]
4|app | 8: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::EnsureGrowable(v8::internal::Handle<v8::internal::OrderedHashSet>) [node /home/app/server.js]
4|app | 9: v8::internal::Runtime_SetGrow(int, v8::internal::Object**, v8::internal::Isolate*) [node /home/app/server.js]
4|app | 10: 0x7a8879046fd
also sometimes this error
4|app | <--- Last few GCs --->
4|app |
4|app | [11385:0x2b893d0] 764692 ms: Mark-sweep 1398.5 (1871.3) -> 1398.5 (1871.3) MB, 27920.5 / 2.1 ms allocation failure GC in old space requested
4|app | [11385:0x2b893d0] 789281 ms: Mark-sweep 1398.5 (1871.3) -> 1398.3 (1797.3) MB, 24586.0 / 4.6 ms last resort
4|app | [11385:0x2b893d0] 797403 ms: Mark-sweep 1398.3 (1797.3) -> 1398.3 (1758.8) MB, 8119.9 / 1.0 ms last resort
4|app |
4|app |
4|app | <--- JS stacktrace --->
4|app |
4|app | ==== JS stack trace =========================================
4|app |
4|app | Security context: 0x7e7bf028799 <JSObject>
4|app | 1: add [native collection.js:~111] [pc=0x7a887d1b539](this=0x13ebc6615671 <Set map = 0x18534a9053d9>,p=0x1d9c6aee7719 <String[24]: 5b9827afc5635e2a08f49b6f>)
4|app | 2: baseUniq [/home/app/node_modules/waterline/node_modules/lodash/index.js:~2670] [pc=0x7a887d4d51a](this=0x243308d07421 <JSGlobal Object>,array=0x13ebc66154d9 <JSArray[469241]>,iteratee=0x13ebc6615531 <JSFunction (sfi = 0x3fc29...
Please help me find which code is blowing up the heap. I tried tools to find out leaks but it only tells memory is leaked not where.
node.js memory-leaks heap
node.js memory-leaks heap
asked Mar 21 at 13:43
Shahid KamalShahid Kamal
5510
asked Mar 21 at 13:43
Shahid KamalShahid Kamal
5510
asked Mar 21 at 13:43
Shahid KamalShahid Kamal
5510
asked Mar 21 at 13:43
Shahid KamalShahid Kamal
5510
asked Mar 21 at 13:43
Shahid KamalShahid Kamal
5510
5510
Are you sure it's a memory leak? i.e. you could first try to increase the max-heap size and see if the error still happens. If yes, maybe check this link which helped me a lot when I had the same problem -> blog.risingstack.com/case-study-node-js-memory-leak-in-ghost
– eol
Mar 21 at 14:11
Thanks I will update after increasing heap size
– Shahid Kamal
Mar 21 at 14:17
As @eol said, try running node --max-old-space-size=8192 <your-entrypoint>.js. We can't really figure out where the leak happens from error you are getting.
– Branko Zivanovic
Mar 21 at 14:18
I got some idea where leak is happening it's a third party library (waterline.js) to query the db. Still testing things. What does old-space means in v8 land? @BrankoZivanovic
– Shahid Kamal
2 days ago
By default, your nodejs process can take 512MB maximum, and when you exceed it's going to crash, just like it did. You can use node --max-old-space-size=2048 index.js to increase it to 2gb or higher, and see if it crashes then, or you may not even be able to profile CPU usage without it if you can't even start a script properly. Good luck!
– Branko Zivanovic
2 days ago
add a comment |
Are you sure it's a memory leak? i.e. you could first try to increase the max-heap size and see if the error still happens. If yes, maybe check this link which helped me a lot when I had the same problem -> blog.risingstack.com/case-study-node-js-memory-leak-in-ghost
– eol
Mar 21 at 14:11
Thanks I will update after increasing heap size
– Shahid Kamal
Mar 21 at 14:17
As @eol said, try running node --max-old-space-size=8192 <your-entrypoint>.js. We can't really figure out where the leak happens from error you are getting.
– Branko Zivanovic
Mar 21 at 14:18
I got some idea where leak is happening it's a third party library (waterline.js) to query the db. Still testing things. What does old-space means in v8 land? @BrankoZivanovic
– Shahid Kamal
2 days ago
By default, your nodejs process can take 512MB maximum, and when you exceed it's going to crash, just like it did. You can use node --max-old-space-size=2048 index.js to increase it to 2gb or higher, and see if it crashes then, or you may not even be able to profile CPU usage without it if you can't even start a script properly. Good luck!
– Branko Zivanovic
2 days ago
Are you sure it's a memory leak? i.e. you could first try to increase the max-heap size and see if the error still happens. If yes, maybe check this link which helped me a lot when I had the same problem -> blog.risingstack.com/case-study-node-js-memory-leak-in-ghost
– eol
Mar 21 at 14:11
Are you sure it's a memory leak? i.e. you could first try to increase the max-heap size and see if the error still happens. If yes, maybe check this link which helped me a lot when I had the same problem -> blog.risingstack.com/case-study-node-js-memory-leak-in-ghost
– eol
Mar 21 at 14:11
Thanks I will update after increasing heap size
– Shahid Kamal
Mar 21 at 14:17
Thanks I will update after increasing heap size
– Shahid Kamal
Mar 21 at 14:17
As @eol said, try running node --max-old-space-size=8192 <your-entrypoint>.js. We can't really figure out where the leak happens from error you are getting.
– Branko Zivanovic
Mar 21 at 14:18
As @eol said, try running node --max-old-space-size=8192 <your-entrypoint>.js. We can't really figure out where the leak happens from error you are getting.
– Branko Zivanovic
Mar 21 at 14:18
I got some idea where leak is happening it's a third party library (waterline.js) to query the db. Still testing things. What does old-space means in v8 land? @BrankoZivanovic
– Shahid Kamal
2 days ago
I got some idea where leak is happening it's a third party library (waterline.js) to query the db. Still testing things. What does old-space means in v8 land? @BrankoZivanovic
– Shahid Kamal
2 days ago
By default, your nodejs process can take 512MB maximum, and when you exceed it's going to crash, just like it did. You can use node --max-old-space-size=2048 index.js to increase it to 2gb or higher, and see if it crashes then, or you may not even be able to profile CPU usage without it if you can't even start a script properly. Good luck!
– Branko Zivanovic
2 days ago
By default, your nodejs process can take 512MB maximum, and when you exceed it's going to crash, just like it did. You can use node --max-old-space-size=2048 index.js to increase it to 2gb or higher, and see if it crashes then, or you may not even be able to profile CPU usage without it if you can't even start a script properly. Good luck!
– Branko Zivanovic
2 days ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55281824%2fstrange-heap-out-of-memory-nodejs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55281824%2fstrange-heap-out-of-memory-nodejs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you sure it's a memory leak? i.e. you could first try to increase the max-heap size and see if the error still happens. If yes, maybe check this link which helped me a lot when I had the same problem -> blog.risingstack.com/case-study-node-js-memory-leak-in-ghost
– eol
Mar 21 at 14:11
Thanks I will update after increasing heap size
– Shahid Kamal
Mar 21 at 14:17
As @eol said, try running node --max-old-space-size=8192 <your-entrypoint>.js. We can't really figure out where the leak happens from error you are getting.
– Branko Zivanovic
Mar 21 at 14:18
I got some idea where leak is happening it's a third party library (waterline.js) to query the db. Still testing things. What does old-space means in v8 land? @BrankoZivanovic
– Shahid Kamal
2 days ago
By default, your nodejs process can take 512MB maximum, and when you exceed it's going to crash, just like it did. You can use node --max-old-space-size=2048 index.js to increase it to 2gb or higher, and see if it crashes then, or you may not even be able to profile CPU usage without it if you can't even start a script properly. Good luck!
– Branko Zivanovic
2 days ago