node: src/uv-common.c:105: uv_err_name: Assertion `0' failed.

[Dave Clements]

Hey,

This error keeps crashing node,

node: src/uv-common.c:105: uv_err_name: Assertion `0' failed.

but it's unpredictable. I've looked it up on the github issues, but
there's not much info about what to actually to do about it, some
think its to do with socket.io etc, but I'm not using socket.io, this
would be the culprit code:

var s=fs.createReadStream(f).once('open',function() {
response.writeHead(200,contentType);
this.pipe(response);
}).once('error',function(e) {
console.log(e);
response.writeHead(500);
response.end();
});

And I tend to be able to create the error using larger files (25mb +),
it can happen on first request or after 5 or 6, or whatever.

Any one got any ideas of how to handle this?

Best,
Dave

[Dave Clements]

anyone?

[Paddy Byers]

Hi,

anyone?

Can anyone else reproduce it?

Are you able to rebuild or debug node to investigate?

The assertion failure indicates that something resulted in an unexpected error code, but without further information it will be hard to identify the root cause. If you could get a stack trace at the point the assertion fails, by building node with symbols and running it under gdb, then that would definitely be a start.

Unless, of course, someone else has seen the problem and looked into it.

Thanks - Paddy 

[Jann Horn]

Several people posted backtraces.

--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mai...

[Paddy Byers]

Hi,

Several people posted backtraces.

OK, my mistake, I hadn't seen the issue (https://github.com/joyent/libuv/issues/206)

Paddy

[Dave Clements]

Hi guys

thanks for your responses, like Jann explained stack traces are
already available, though it would have been helpful if i'd have
linked to the issue, there seems to be a lot of silence on this
topic. I updated to node 0.6.0, and the problem prevails. its only a
guess, but I think its something to do with pipe,

If anyone could shed more light on this I'd be very grateful, Even if
it is a bug, is there a way to catch and handke this type of error?


Dave

[Ben Noordhuis]

It's a bug in libuv. Expect it to be fixed in the next few days.

[Dave Clements]

excellent, thanks Ben!

On Nov 7, 7:00 am, Ben Noordhuis <i...@bnoordhuis.nl> wrote:

[Alexandro David Campos]

any news regarding this fix I am also seeing this issue and making my
cluster workers crash, can you please help me figure out a soution?

On 7 nov, 01:00, Ben Noordhuis <i...@bnoordhuis.nl> wrote:

[Ben Noordhuis]

On Wed, Nov 23, 2011 at 18:01, Alexandro David Campos
<medw...@gmail.com> wrote:
> any news regarding this fix I am also seeing this issue and making my
> cluster workers crash, can you please help me figure out a soution?

It should be fixed in 0.6.2. Can you open an issue if you still run into it?

Make sure to test with a clean build (`make distclean`) and please
include all relevant details in the bug report, including the output
of `node -v`. A test case is much appreciated too.