What version of 1.9.2 are you on? I haven't seen malloc errors that often with 1.9 and unless you start debugging with GDB, it will be a bit hard to know where they are coming from. My guess is that you have a C extension that's not behaving. Make sure to uninstall all your gems and use a gemset. That might help.
- Matt On Tue, Jul 19, 2011 at 2:29 PM, Ylan <[email protected]> wrote: > Hey Everyone, > > Lately I have been getting some weird ruby errors (using rvm 1.9.2). I > can't really tell when they happen. Sometimes it's running bundler, > sometimes rake, sometimes spork or just running individual tests using > Test::Unit. > > The errors looks something like this: > > $rake db:migrate > ruby(3203,0x7fff70a1acc0) malloc: *** error for object 0x100000000: pointer > being freed was not allocated > *** set a breakpoint in malloc_error_break to debug > Abort trap > > I already deleted the ruby version with rvm and reinstalled 1.9.2, > re-bundled all my gems, etc. But it came back. > > Usually, if I just run the command again, it is successful, so I can't > really re-create the conditions. It's getting to be pretty annoying. > > Has anyone seen this before? > > Thanks, > > -- > Ylan. > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
