Why not be recovered memory

52 views
Skip to first unread message

Liujin Wu

unread,
Aug 26, 2016, 8:37:43 AM8/26/16
to nodejs
  
var showMem = function(num) {  
    var mem = process.memoryUsage();  
    var format = function(bytes) {  
         return (bytes/1024/1024).toFixed(2)+'MB';  
    };  
    console.log('Process: heapTotal '+format(mem.heapTotal) + ' heapUsed ' + format(mem.heapUsed) + ' rss ' + format(mem.rss));  
    console.log(num+'----------------------------------------');  
};

showMem(1);
(function(){
var array = [];
for(var i = 0;i<1024*1024*10;i++){
array.push(i);
}
showMem(2);
array = null;
})()



setInterval(function(){
showMem(3);
},3000)



Axel Kittenberger

unread,
Sep 2, 2016, 9:54:25 AM9/2/16
to nodejs
Because the V8 only fires up the garbage collector to recover memory when it thinks it needs to.

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscribe@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/bf40d54a-9d67-4fe6-ba1d-b671d641098f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages