Menu
▾
▴
Re: [Rubycocoa-talk] A potential bug to watch out for...
|
From: Gregory C. <gr...@in...> - 2009-05-16 22:16:48
|
Hi Allison, I installed MacRuby 0.4 one weekend to play with it, but on Monday when I was back to work on my RubyCocoa app I found that it would no longer build and run! Uninstalled MacRuby and everything was fine. Greg > The bug doesn't occur in all apps - just in the biggest app that I > have written to date in RubyCocoa (naturally!), though as I said, in > that app, it happens in numerous places (changing a selection in a > group of objects, responding to a timer, serialising an object, etc > etc etc). I'm trying to find a nice small example that reproduces > the bug reliably, but without luck so far. I'll post it once I've > found a good, reliable way of making things blow up. > > Still, based on your experience, it's looking like MacRuby is the > culprit. This does make some sense... > > Alli > > > Le 16 mai 09 à 22:57, Duncan McGregor a écrit : > >> I've had that Xcode trace in my console (various addresses) for at >> least the past few days, before and after updating to 10.5.7, so >> maybe that isn't related to your [BUG]. >> >> My app still passes all its tests without your 'object allocation >> during garbage collection phase' issue, and, to pick one random >> example that we both could run, so does CGPDFViewer. So maybe its >> MacRuby? >> >> Cheers >> >> Duncan >> www.VelOCRaptor.com >> >> On 16 May 2009, at 21:40, Allison Newman wrote: >> >>> Hi everyone, >>> >>> I installed OS X 10.5.7 yesterday, as well as MacRuby 0.4. Since >>> then, whenever I run one of my RubyCocoa apps, I get the following >>> bug: >>> >>> [BUG] object allocation during garbage collection phase >>> ruby 1.8.6 (2008-08-11) [universal-darwin9.0] >>> >>> The application has been stable for over 6 months. Just to be >>> sure, I recovered a version from 3 months ago off TimeMachine, and >>> it still doesn't work, so the bug is definately coming from the >>> environment, not the app. Worse yet, the same bug appears in >>> multiple different places in the app, not just in one particular >>> part of the code, for example during a call to an NSEncoding >>> method, or whilst handling an NSTimer event. >>> >>> Checking the console logs, I now see this appearing all of the >>> time for RubyCocoa apps, when it has never before appeared in the >>> logs: >>> 16/05/09 22:33:20 [0x0-0xa60a6].com.apple.Xcode[2048] >>> Xcode(2048,0xb0103000) malloc: free_garbage: garbage ptr = >>> 0x45d8240, has non-zero refcount = 1 >>> >>> I'll typically see this trace about 50 times during the execution >>> of any RubyCocoa app. >>> >>> Apparently this is a bug in the Ruby interpretor. I don't know >>> which of these installs (10.5.7 or MacRuby) borked my machine, or >>> indeed if it was an interaction beween the two of them, but be >>> aware that you may have this problem before installing either. >>> >>> Alli >>> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables >> unlimited royalty-free distribution of the report engine >> for externally facing server and web deployment. >> http://p.sf.net/sfu/businessobjects_______________________________________________ >> Rubycocoa-talk mailing list >> Rub...@li... >> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects_______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |
