it seems like the process went into an infinite loop. if you use linux, you can use strace to track syscalls
$ strace -p <pid> $ node debug -p <pid> and `backtrace` commands may help. gdb is another tool, it can report native backtrace. $ gdb -p <pid> and type `bt` On Monday, October 10, 2016 at 9:53:03 PM UTC+8, Bgsosh wrote: > > Hi, > > I'm having a tough time tracking down an issue we currently have in > production. Our node processes will sometimes suddenly spike in CPU usage, > and then stay pegged at 100% until restarted. > > I'm not able to reproduce on development machine. Could anyone offer any > tips for tracking this down? Any advice would be appreciated as I'm > currently not getting enough sleep! > > Thank you > > Bg > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/1d171e4d-189c-48dc-ac37-344fbbd40ef1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
