Although it's a CPU issue, a heapdump could still be useful. There are ways
to do it, such as https://www.npmjs.com/package/heapdump. You can try to
get a dump once the CPU goes up and simply load it into Chrome dev tools -
to see what is going on, perhaps there's a hint.
If while at 100% you
You definitely want to flamegraph the
processes:
http://www.brendangregg.com/blog/2014-09-17/node-flame-graphs-on-linux.html
This problem is often caused by the GC when you approach V8's heap size
limit (which is around 1.5gb). So if you see your procs using around that
much memory, you'll
it seems like the process went into an infinite loop.
if you use linux, you can use strace to track syscalls
$ strace -p
$ node debug -p
and `backtrace` commands may help.
gdb is another tool, it can report native backtrace.
$ gdb -p
and type `bt`
On Monday, October 10, 2016 at 9:53:03
Hello Bg,
I faced a similar problem and after searching everywhere and checking every
source possible, it turned out to be a faulty URL. An encoding/decoding
problem which when passed through express it caused an infinite loop
somewhere in the express library. So a way to check that might be
