CODEWITHSUNDEEP
node.jsgarbage-collectionv8
selftaught91
selftaught91

Reputation: 7471

when does the garbage collector of v8 engine of chrome is activated by default in nodejs

If my nodejs memory is reached upto 1.5GB and then i am not applying any load on it and the system is idle for 30 minutes then also garbage collector is not freeing the memory

Upvotes: 1

Views: 954

Answers (1)

rsp
rsp

Reputation: 111424

It's impossible to say anything specific, like "why gc is not collecting the garbage" as you ask in the comments, when you say nothing about what your program is doing or how the code looks like.

I can only point you to good explanation of how GC works in Node and explain how to run GC manually to see if that helps. When you run node with the --expose-gc flag, then you can use:

global.gc();

in your code. You can try to run that code in a timeout, on a regular interval or at any other specific moment and see if that frees your memory. If it does, that would mean that the GC was indeed not running and that was the problem. If that doesn't free your memory that could mean that the problems is not with the GC not running, but rather not being able to free anything.

Memory not being freed after manual GC invocation would mean that you have some memory leak or that you use so much memory that cannot be freed by the GC.

If the memory is freed after running GC manually it could mean that it is not running by itself, maybe because you are doing a very long, blocking operation that doesn't give the event loop any chance to run. For example having a long running for or while loop could give such an effect.

Not knowing anything about your code or what it does, it's not possible to give you any more specific solution to your problem.

If you want to know how and when the GC in Node works, then there is some good documentation online.

There is a nice article by StrongLoop about how the GC works:

Also this article by Daniel Khan is worth reading:

It's possible that the GC is running but it can't free any memory because you have some memory leak. Without seeing an actual code or even an explanation of what it does it's realy impossible to say more.

Upvotes: 2

Related Questions