Joshua, it looks then that our issues are totally unrelated. On my side it's definitely about watchers. Node v0.6 had much bigger problems, crashed when closing and then reopening watcher for same file, Node v0.8 seems to have that fixed, but still it looks it's not perfectly stable in that functionality, I'm sure it will get better with new releases.
On Friday, August 10, 2012 5:28:11 PM UTC+2, Joshua Gross wrote: > > So I narrowed it down to bcrypt and after reinstalling it, it works fine > for me. Mariusz, could you have a similar issue? > > Joshua Gross > Christian / SpanDeX, Inc. / BA of Computer Science, UW-Madison 2013 > 414-377-1041 / http://www.joshisgross.com / http://www.spandex.io > > > > On 10 August 2012 06:56, Mariusz Nowak <[email protected] > <javascript:>>wrote: > >> On my side it's plain Node.js and strictly JavaScript modules. >> >> It started to happen when I started to close fs watchers on the way. >> Errors happen at random times, and when I tried to narrow it. I found out >> that they happen on calls to fs.writeFile (or other functions that do >> changes to file system), also it's not same Error that is thrown every >> time, basically there are many flavors of them, ones that happened: >> >> Segmentation fault: 11 >> Bus error: 10 >> Error: write EBADF >> libev: ev_io_stop called with illegal fd (must stay constant after start!) >> pointer being freed was not allocated >> incorrect checksum for freed object >> >> It's impossible to narrow it down (I wanted to do it), I just reduce some >> number of (any) tests and it works ok, it's not bound to specific test, and >> as I said it started to happen when I started to close file watchers. >> Those tests also pass perfectly in any other environment (Linux, >> Windows). You may try it yourself ( I work on Node v0.8.6 installed from >> binary package): >> npm install git://github.com/medikoo/node-ext.git >> npm test >> >> >> On Friday, August 10, 2012 1:08:55 PM UTC+2, Ben Noordhuis wrote: >> >>> On Fri, Aug 10, 2012 at 7:39 AM, Joshua Gross <[email protected]> >>> wrote: >>> > Just upgraded to node 0.8.6 and I'm writing a suite of unit tests >>> using >>> > Selenium and Webdriverjs - all that to say, I'm seeing this >>> consistently at >>> > the same point in my tests: >>> > >>> > DEBUG: node(39081,0x1027c9000) malloc: *** error for object >>> 0x100617358: >>> > pointer being freed was not allocated >>> > *** set a breakpoint in malloc_error_break to debug >>> > >>> > That's in my server log. I realize this is probably useless without >>> further >>> > details, so tell me how I can get relevant details and I'll do what I >>> can. >>> > >>> > Joshua Gross >>> > Christian / SpanDeX, Inc. / BA of Computer Science, UW-Madison 2013 >>> > 414-377-1041 / http://www.joshisgross.com / http://www.spandex.io >>> >>> First thing to check is if your application uses native add-ons >>> (directly or indirectly). If it doesn't, it's a node or possibly a >>> system bug. If it does, you will need to apply the principle of >>> exclusion to find the offending add-on. >>> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> > > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
