Segfault on FreeBSD

[sigmike]

I'm running this simple source:

var http = require("http");

http.createServer(function(request, response) {
  response.writeHead(200, {"Content-Type": "text/plain"});
  response.write("Hello World");
  response.end();
}).listen(5000);

It works fine until I hit Ctrl+C: it segfaults.

Here's the backtrace:

#0  0x000000080226f469 in swapcontext () from /lib/libthr.so.3
#1  0x000000080226f062 in sigaction () from /lib/libthr.so.3
#2  <signal handler called>
#3  0x00000008024f344a in _umtx_op () from /lib/libc.so.7
#4  0x00000008024e2c24 in sem_timedwait () from /lib/libc.so.7
#5  0x0000000000b53ef8 in v8::base::Semaphore::Wait ()
#6  0x00000000008c7e84 in v8::internal::SweeperThread::Run ()
#7  0x0000000000b5594d in v8::base::ThreadEntry ()
#8  0x000000080226a4f5 in pthread_create () from /lib/libthr.so.3
#9  0x0000000000000000 in ?? ()

I'm running FreeBSD 10.1-RELEASE with node installed from the ports.

If I run a script that contains only a console.log it doesn't crash when it exits.

[sigmike]

node -v returns v0.12.0

[vba-ds]

Have a same problem on FreeBSD 10.1-RELEASE-p5 with nodejs 0.12.0.

#0  0x000000080225e469 in swapcontext () from /lib/libthr.so.3
[New Thread 803407400 (LWP 100767/v8:SweeperThrea)]
[New Thread 803407000 (LWP 100374/v8:SweeperThrea)]
[New Thread 803406c00 (LWP 100331/v8:SweeperThrea)]
[New Thread 803406800 (LWP 100214/OptimizingCompi)]
[New Thread 803406400 (LWP 100081/node)]

(gdb) bt full
#0  0x000000080225e469 in swapcontext () from /lib/libthr.so.3
#1  0x000000080225e062 in sigaction () from /lib/libthr.so.3
#2  <signal handler called>
#3  0x00000008024e244a in _umtx_op () from /lib/libc.so.7
#4  0x00000008024d1c24 in sem_timedwait () from /lib/libc.so.7
#5  0x0000000000b3ce08 in v8::base::Semaphore::Wait ()
#6  0x00000000008c46c4 in v8::internal::SweeperThread::Run ()
#7  0x0000000000b3e52d in v8::base::ThreadEntry ()
#8  0x00000008022594f5 in pthread_create () from /lib/libthr.so.3
#9  0x0000000000000000 in ?? ()

(gdb) t 5
[Switching to thread 5 (Thread 803406400 (LWP 100081/node))]#0  0x000000080259904a in kevent () from /lib/libc.so.7

(gdb) bt full
#0  0x000000080259904a in kevent () from /lib/libc.so.7
#1  0x0000000000b3bad7 in uv__io_poll (loop=0x111b5c0, timeout=<value optimized out>) at ../deps/uv/src/unix/kqueue.c:142
        events = {{ident = 0, filter = 0, flags = 0, fflags = 0, data = 0, udata = 0x0}}
        events = {{ident = 6, filter = -1, flags = 1, fflags = 0, data = 0, udata = 0x0}, {ident = 9, filter = -1, flags = 1, fflags = 0, data = 0, udata = 0x0},


...stripped...

On Ubuntu 14.04 (3.13.0-45-generic) the same code works fine.

[misterdjules]

I haven't had time to reproduce/investigate, but adding it to 0.12.1 to make sure we take care of it asap.

[misterdjules]

@tjfontaine Assigning to you as discussed during the core team meeting. Please assign to @trevnorris when he can use a FreeBSD 10.1 VM somewhere. Thank you!

[trevnorris]

Was finally able to reproduce. Though I'm not sure this is a Node thing. Might be a libuv problem?

[trevnorris]

Here's a simplified test:

require('http').createServer().listen(0, function() {
  process.kill(process.pid, 'SIGINT');
});

Still narrowing down why this is happening.

[trevnorris]

I've confirmed this is also an issue in io.js. Still investigating why this could possibly happen.

[trevnorris]

More stack trace info using latest libuv:

#0  0x000000080291f469 in swapcontext () from /lib/libthr.so.3
#1  0x000000080291f062 in sigaction () from /lib/libthr.so.3
#2  <signal handler called>
#3  0x0000000802c79a1a in kill () from /lib/libc.so.7
#4  0x000000000137f149 in uv_kill (pid=41450, signum=2) at ../deps/uv/src/unix/process.c:512
#5  0x00000000012c7dca in node::Kill (args=@0x7fffffffddb0) at ../src/node.cc:1960
#6  0x0000000000b583bc in v8::internal::FunctionCallbackArguments::Call (this=0x7fffffffdeb0, f=0x12c7d30 <node::Kill(v8::FunctionCallbackInfo<v8::Value> const&)>)
    at ../deps/v8/src/arguments.cc:33
#7  0x0000000000ba6a15 in v8::internal::HandleApiCallHelper<false> (args=
        {<v8::internal::Arguments> = {<v8::internal::Embedded> = {<No data fields>}, length_ = 4, arguments_ = 0x7fffffffe0c0}, <No data fields>}, isolate=0x803853000)
    at ../deps/v8/src/builtins.cc:1139
#8  0x0000000000ba64b5 in v8::internal::Builtin_Impl_HandleApiCall (args=
        {<v8::internal::Arguments> = {<v8::internal::Embedded> = {<No data fields>}, length_ = 4, arguments_ = 0x7fffffffe0c0}, <No data fields>}, isolate=0x803853000)
    at ../deps/v8/src/builtins.cc:1156
#9  0x0000000000b9edb0 in v8::internal::Builtin_HandleApiCall (args_length=4, args_object=0x7fffffffe0c0, isolate=0x803853000) at ../deps/v8/src/builtins.cc:1155

[trevnorris]

I'm going to need more help to continue with this issue.

/cc @joyent/node-coreteam

[indutny]

Oh yeah, I seen it once. Looking...

[indutny]

The problem disappears if I'll remove SA_RESETHAND... Looking further