{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/a5bb45388c05824035c3e0f767e3a190?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"a5bb45388c05824035c3e0f767e3a190","url":"https://api.github.com/users/tommypowerz","login":"tommypowerz","id":1094165},"labels":[],"assignee":null,"updated_at":"2011-11-14T22:41:05Z","comments":35,"closed_at":null,"url":"https://api.github.com/repos/joyent/libuv/issues/206","body":"my node server.js is breaking from time to time with this error:\r\n\r\nsrc/uv-common.c:92: uv_err_name: Assertion `0' failed.\r\n\r\n\r\nit uses socket.io and get many connections...\r\n\r\nis there a way to try/catch this somehow in my server?\r\n\r\ni'm totally lost.. there are no more informations when it crashes....\r\n\r\nthanks in advance for your help guys..","html_url":"https://github.com/joyent/libuv/issues/206","title":"src/uv-common.c:92: uv_err_name: Assertion `0' failed.","number":206,"id":1790533,"created_at":"2011-10-01T02:25:56Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/3d43d9038ab645ecb2e3a1df2951d30a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3d43d9038ab645ecb2e3a1df2951d30a","url":"https://api.github.com/users/bnoordhuis","login":"bnoordhuis","id":275871},"updated_at":"2011-11-14T22:41:05Z","url":"https://api.github.com/repos/joyent/libuv/issues/comments/2737883","body":"On Mon, Nov 14, 2011 at 22:38, Russ Bradberry\r\n<reply@reply.github.com>\r\nwrote:\r\n> I also got a broken pipe:\r\n>\r\n>    Program received signal SIGPIPE, Broken pipe.\r\n>    0x00002aaaac22a6bb in write () from /lib64/libpthread.so.0\r\n>    (gdb) backtrace\r\n>    #0  0x00002aaaac22a6bb in write () from /lib64/libpthread.so.0\r\n>    #1  0x00000000007fd375 in uv__write (stream=0xc955c0) at src/unix/stream.c:400\r\n>    #2  0x00000000007fe5ef in uv_write2 (req=0xcaa958, stream=0xc955c0, bufs=0x7fff3601eb70, bufcnt=1, send_handle=0x0, cb=0x53a000 <node::StreamWrap::AfterWrite(uv_write_s*, int)>) at src/unix/stream.c:881\r\n>    #3  0x00000000007fe680 in uv_write (req=0xcaa958, stream=0xc955c0, bufs=0x7fff3601eb70, bufcnt=1, cb=0x53a000  <node::StreamWrap::AfterWrite(uv_write_s*, int)>) at src/unix/stream.c:902\r\n>    #4  0x000000000053a672 in node::StreamWrap::Write (args=@0x7fff3601ebc0) at ../src/stream_wrap.cc:313\r\n>    #5  0x00001e33f5cd116a in ?? ()\r\n>    #6  0x00007fff3601ec18 in ?? ()\r\n>    #7  0x00007fff3601ec20 in ?? ()\r\n>    #8  0x0000000000000001 in ?? ()\r\n>    #9  0x0000000000000000 in ?? ()\r\n\r\nIt's an artefact of how gdb reports some signals: it reports them even\r\nif the program ignores them. `handle SIGPIPE nostop noprint` makes gdb\r\nignore them as well.","id":2737883,"created_at":"2011-11-14T22:41:05Z"}}