I have same issue when I do a lot of writes and reads to files and additionally I'm using a lot of watchers.
However I'm not sure whether it affects just OSX 10.8, anyway it surely affects just OSX. I've looked on the web and in most sources it is said it's a OS issue not Node.js, I hope though it's gonna be fixed somehow, for a time being I feel a bit helpless. Thankfully it just affects tests not real application on my side, so I can move on with it. On Friday, August 10, 2012 7:39:08 AM UTC+2, Joshua Gross 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 > > -- 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
