I am going to suggest just old fashioned debugging. Find a scenario you can reproduce the error as close to 100% as possible. Then remove every dependency from the app and verify that your test case no longer causes the crash. Then just re add dependencies one by one until the issue again appears 100% of the time.
At least that way we will have something to go off of. -Mark On Wednesday, July 20, 2011 at 3:51 PM, Ylan wrote: > On Wednesday, July 20, 2011 11:10:05 AM UTC-7, Matt Aimonetti wrote: > > Not sure if that's the root cause (probably not) but why do you use hpricot > > AND nokogiri? > > > I am not using neither directly. hpricot is declared in my Gemfile and > according to the commit message it says it was needed by html2haml (but I > can't verify that). > > Nokogiri is being installed as a dependency of another of my gems, namely > savon (which you recommended by the way: Thanks!). > > > you also don't need the json gem since it's now packaged in 1.9. > > > That is being pulled in by active merchant, not me directly. > > > Try not loading ruby-debugger19 and see if that's the problem. > > > I'll try that, but don't I need it to be able to run the debugger? > > In any case, it doesn't seem to work. I removed hpricot and ruby-debugger19 > and bundled again. First command I tried bombed: > > $ rails s > ruby(3336,0x7fff70a1acc0) malloc: *** error for object 0x100000000: pointer > being freed was not allocated > *** set a breakpoint in malloc_error_break to debug > Abort trap > > > The second time around it ran fine. > > Thanks! > > -- > Ylan > > -- > SD Ruby mailing list > [email protected] (mailto:[email protected]) > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
