spawn ENOMEM: Memory leak in 1.19.1?
-
@djensen47 Also for what it's worth, MongoDB also tends to allocate as much memory as is free, for its own use, so it might not actually be NodeBB (although it doesn't hurt to check)
It doesn't usually cause issues with running out of memory, but occasionally can. This is warded off with swapfile usage.
-
@julian Swap won't solve a memory leak though. In fact, it'll just hide the issue until the server is unmanageably slow, no?
Also, this is new behavior that started sometime between version 1.17 and 1.19 (no issues on 1.16).
I'm replying because we ran into the issue again.
-
-
Today the node processes are at 32% and 30% of memory.
Redis is steady at 2.6% (roughly same as before).I can keep going but eventually it's just going to keep growing until all the memory is consumed and then it goes to swap and because the memory isn't freeing up, it's not going to help.
It's a slooow leak but it's a leak.
-
@djensen47 maybe it's the node-side db cache. I'm not sure what kind of memory limits we set for it. Does the memory usage grow quickly at first and then slow down approaching an asymptote?
-
-
@PitaJ said in spawn ENOMEM: Memory leak in 1.19.1?:
Does the memory usage grow quickly at first and then slow down approaching an asymptote?
I believe so.
