Just started playing around with node.js, absolutely impressive &
fantastic so far.
Anyway, I think I found an easily reproducible segmentation fault:
seg_fault.js
------------------------------------------------------
new node.http.Server(function (req, res) {
var ls = new node.Process("ls -lah");
ls.onOutput = function(chunk) {
res.sendHeader(200, [["Content-Type", "text/plain"]]);
res.sendBody(chunk || "");
res.finish();
};
}).listen(8001);
puts("Server running at
http://127.0.0.1:8001/");
------------------------------------------------------
triggering the seg fault:
------------------------------------------------------
$ ab -n 1000
http://localhost:8001/
Benchmarking localhost (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Test aborted after 10 failures
apr_socket_connect(): Connection refused (61)
Total of 379 requests completed
------------------------------------------------------
The fact that no matter how often I run this I always gets the
segfault at exactly 379 connections makes me think it's probably some
system process limit being hit. Speaking of which, I used Ubuntu 9.04
Server Edition for my tests.
Anyway, let me know if I can be of any help providing more data. Keep
up the fantastic work!
-- Felix Geisendörfer aka the_undefined