NodeJS memory spike causing heap out of memory
I am doing a testing on potential issue causing my app to die on javascript heap out of memory. I tried to make the heap size smaller to reproduce a similar issue.
I set the max-old-space-size to 5mb and inspected it on Chrome:
node --inspect --max-old-space-size=5 app.js
The following is my app.js code for increasing the memory usage:
const express = require('express')
const app = express()
let port = process.env.SERVER_PORT || 3333
var test =
setInterval(() => {
test.push(
process.memoryUsage()
)
}, 1)
app.listen(port, () => {
console.log('Server is started on ' + port + ' with pid ' + process.pid)
})
... trying to spam the service and record the changes.
The following images are the result of the first memory snapshot warning from chrome.
This is the common data across the service:
This shows the spike right before the memory warning thrown by Chrome's debugger:
This proved that the spike is containing the entire array generated by app.js and also all the system file:
I need help on understanding why the constructor suddently comes out, causes the heap memory issue and kills the service.
javascript node.js debugging
edited Jan 2 at 18:18
blex
12.4k12246
asked Jan 2 at 18:04
Cheong Hao YoongCheong Hao Yoong
63
add a comment |
I am doing a testing on potential issue causing my app to die on javascript heap out of memory. I tried to make the heap size smaller to reproduce a similar issue.
I set the max-old-space-size to 5mb and inspected it on Chrome:
node --inspect --max-old-space-size=5 app.js
The following is my app.js code for increasing the memory usage:
const express = require('express')
const app = express()
let port = process.env.SERVER_PORT || 3333
var test =
setInterval(() => {
test.push(
process.memoryUsage()
)
}, 1)
app.listen(port, () => {
console.log('Server is started on ' + port + ' with pid ' + process.pid)
})
... trying to spam the service and record the changes.
The following images are the result of the first memory snapshot warning from chrome.
This is the common data across the service:
This shows the spike right before the memory warning thrown by Chrome's debugger:
This proved that the spike is containing the entire array generated by app.js and also all the system file:
I need help on understanding why the constructor suddently comes out, causes the heap memory issue and kills the service.
javascript node.js debugging
edited Jan 2 at 18:18
blex
12.4k12246
asked Jan 2 at 18:04
Cheong Hao YoongCheong Hao Yoong
63
add a comment |
I am doing a testing on potential issue causing my app to die on javascript heap out of memory. I tried to make the heap size smaller to reproduce a similar issue.
I set the max-old-space-size to 5mb and inspected it on Chrome:
node --inspect --max-old-space-size=5 app.js
The following is my app.js code for increasing the memory usage:
const express = require('express')
const app = express()
let port = process.env.SERVER_PORT || 3333
var test =
setInterval(() => {
test.push(
process.memoryUsage()
)
}, 1)
app.listen(port, () => {
console.log('Server is started on ' + port + ' with pid ' + process.pid)
})
... trying to spam the service and record the changes.
The following images are the result of the first memory snapshot warning from chrome.
This is the common data across the service:
This shows the spike right before the memory warning thrown by Chrome's debugger:
This proved that the spike is containing the entire array generated by app.js and also all the system file:
I need help on understanding why the constructor suddently comes out, causes the heap memory issue and kills the service.
javascript node.js debugging
edited Jan 2 at 18:18
blex
12.4k12246
asked Jan 2 at 18:04
Cheong Hao YoongCheong Hao Yoong
63
I am doing a testing on potential issue causing my app to die on javascript heap out of memory. I tried to make the heap size smaller to reproduce a similar issue.
I set the max-old-space-size to 5mb and inspected it on Chrome:
node --inspect --max-old-space-size=5 app.js
The following is my app.js code for increasing the memory usage:
const express = require('express')
const app = express()
let port = process.env.SERVER_PORT || 3333
var test =
setInterval(() => {
test.push(
process.memoryUsage()
)
}, 1)
app.listen(port, () => {
console.log('Server is started on ' + port + ' with pid ' + process.pid)
})
... trying to spam the service and record the changes.
The following images are the result of the first memory snapshot warning from chrome.
This is the common data across the service:
This shows the spike right before the memory warning thrown by Chrome's debugger:
This proved that the spike is containing the entire array generated by app.js and also all the system file:
I need help on understanding why the constructor suddently comes out, causes the heap memory issue and kills the service.
javascript node.js debugging
javascript node.js debugging
edited Jan 2 at 18:18
blex
12.4k12246
asked Jan 2 at 18:04
Cheong Hao YoongCheong Hao Yoong
63
edited Jan 2 at 18:18
blex
12.4k12246
asked Jan 2 at 18:04
Cheong Hao YoongCheong Hao Yoong
63
edited Jan 2 at 18:18
blex
12.4k12246
edited Jan 2 at 18:18
blex
12.4k12246
edited Jan 2 at 18:18
blex
12.4k12246
12.4k12246
asked Jan 2 at 18:04
Cheong Hao YoongCheong Hao Yoong
63
asked Jan 2 at 18:04
Cheong Hao YoongCheong Hao Yoong
63
asked Jan 2 at 18:04
Cheong Hao YoongCheong Hao Yoong
63
63
add a comment |
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
});
}
});
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%2f54011085%2fnodejs-memory-spike-causing-heap-out-of-memory%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
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.
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%2f54011085%2fnodejs-memory-spike-causing-heap-out-of-memory%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
