On Thu, May 10, 2012 at 12:48 PM, Erik Dubbelboer <[email protected]> wrote: > We have an application that handles a couple of http and udp requests per > second. It uses no C modules, only modules written in javascript. > > From time to time the application will hang. Attaching strace at this point > will only output lines of: > > futex(0x10e36c8, FUTEX_WAKE_PRIVATE, 1) = 1 > > As you can see the call does wake up a process but for some reason it's > still in a deadlock. Since we only use javascript code it is most likely a > bug in nodejs. > > The problem is that I have no idea which conditions cause the deadlock. It > can takes days (sometimes over a week) for this to happen. I haven't been > able to reproduce the deadlock in a development environment. > > What would be the best way to hunt down this bug?
Attach with gdb and inspect the call stack. Alternatively, make a core dump with gcore and send it my way, I can probably figure out what's going on. What do `uname -a`, `node -v` and `ldd node` say? Is your application using TLS or crypto? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
