-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crash on iojs-1.6.x #1228
Comments
That looks like a double close or a corrupted libuv handle. Can you check the debug binary's backtrace with gdb or lldb? |
sure. I went to master, but it tells me 'let' is a reserved keyword so I went back to tag v1.6.1 and reconfigured with I attached gdb to the running process and continued.. is there an easier way of launching iojs without having to do that? without the ability to relaunch iojs, I'm slightly impaired in my ability to do dev... I'll try and work around it for now |
You can turn on core dumps ( |
There might be some core dumps already there in |
just checked and there aren't any... I hadn't known of that feature until now, actually. so far still no crashes... seems go go wonky when I'm right about the time I'm gonna get a feature done, so here's to getting things done 👍 it'll crash again soon... cheers |
ok, it just happened to me again, however there is still nothing inside of /cores. it happened this time when I pressed ctrl-c to close it.. I do remember on sunday it was crashing though. I re-ran EDIT: just added it to my zshrc, so in case I accidentally change terminals again it'll dump.. :) |
is this related to b64983d ? I can do further investigation if necessary
EDIT: gonna upgrade to 1.6.2. let you know if something changes. |
still happening ... quite regularly... I can send the core dumps out if someone wants them. I have 3 now. EDIT: holy shit ... they're 1.2G each, so I'll keep a few around in case |
@heavyk Can you post full backtraces? That's |
sure
|
btw, since I've upgraded to 1.6.2, I've not crashed since (but then again, it didn't crash all day the other day either.) EDIT: if there's a way to truncate the dump, even still, if it helps, I'll still be glad to give it to you (only thing "private" is some self signed certs I made last week). want me to xz and put it on a server? |
I see you're using the fsevents module. That module has a couple of known issues (see e.g. fsevents/fsevents#52) that I haven't gotten around to fixing yet. Closing, let's move this to the fsevents issue tracker. |
cool. thanks. |
since upgrading from 1.5.1, I regularly get this error:
it's the third time today, so there will be more opportunities to debug. I'm checking out master and recompiling with --debug now, so I can give more info if it happens again
I'm doing a lot of spdy development, so it could perhaps have something to do with openssl upgrade - dunno. I've also noticed another error lately too, since the 1.6.1 upgrade it's crashed on socket write after hangup - but I don't know if it's related - perhaps to the writev commit
how can I debug this better?
OSX 10.9.5
The text was updated successfully, but these errors were encountered: