I'll create a core dump next time it happens.
Yes we are using crypto.createHash('md5') but only for small strings
of max 64 characters.
erik@rtbuyer-us:~$ uname -a
Linux rtbuyer-us 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
erik@rtbuyer-us:~$ node -v
v0.6.17
erik@rtbuyer-us:~$ ldd `which node`
linux-vdso.so.1 => (0x00007fff8e57f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fd790cc0000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fd790ab8000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0
(0x00007fd79085b000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
(0x00007fd790493000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fd79028f000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007fd78ff8e000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fd78fc94000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007fd78fa7e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007fd78f860000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd78f4a3000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd790ee5000)
On Thu, May 10, 2012 at 2:19 PM, Ben Noordhuis <[email protected]> wrote:
> 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
--
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
