[nodejs] Re: [libuv] silent crash on large response + closing connection from client

2012-08-06 Thread Felix Halim
On Tue, Aug 7, 2012 at 1:28 AM, Felix Halim wrote: > I am using (the updated) Ryan Dahl's simple webserver: > > https://gist.github.com/1249783 > > I modify the webserver.c so that instead of responding with a simple > "hello world", it send a large response about 500KB. > > Then these steps below

[nodejs] Re: [libuv] silent crash on large response + closing connection from client

2012-08-06 Thread Ben Noordhuis
On Mon, Aug 6, 2012 at 8:05 PM, Felix Halim wrote: > On Tue, Aug 7, 2012 at 1:28 AM, Felix Halim wrote: >> I am using (the updated) Ryan Dahl's simple webserver: >> >> https://gist.github.com/1249783 >> >> I modify the webserver.c so that instead of responding with a simple >> "hello world", it s

[nodejs] Re: [libuv] silent crash on large response + closing connection from client

2012-08-06 Thread Felix Halim
On Tue, Aug 7, 2012 at 3:47 AM, Ben Noordhuis wrote: > No, libuv (and node.js) handles that fine. Chances are high that the > bug is in your application. After further investigation, valgrind says that it got a SIGPIPE: ==17980== Process terminating with default action of signal 13 (SIGPIPE) ==1

[nodejs] Re: [libuv] silent crash on large response + closing connection from client

2012-08-07 Thread Ben Noordhuis
On Tue, Aug 7, 2012 at 6:05 AM, Felix Halim wrote: > On Tue, Aug 7, 2012 at 3:47 AM, Ben Noordhuis wrote: >> No, libuv (and node.js) handles that fine. Chances are high that the >> bug is in your application. > > After further investigation, valgrind says that it got a SIGPIPE: > > ==17980== Proc

Re: [nodejs] Re: [libuv] silent crash on large response + closing connection from client

2012-08-07 Thread Felix Halim
On Tue, Aug 7, 2012 at 8:42 PM, Ben Noordhuis wrote: > On Tue, Aug 7, 2012 at 6:05 AM, Felix Halim wrote: >> On Tue, Aug 7, 2012 at 3:47 AM, Ben Noordhuis wrote: >>> No, libuv (and node.js) handles that fine. Chances are high that the >>> bug is in your application. >> >> After further investiga