On Nov 29, 2007, at 7:12 PM, Mark O'Neill wrote:
> Hi Dave,
>
> On 30 Nov 2007, at 00:07, Dave Wooldridge wrote:
>
>> Of course, depending on the needs of your own projects, your
>> mileage may
>> vary, but if anyone finds themselves needing to release their app for
>> Leopard before this Leopard-related memory leak is fixed, you may
>> want to
>> try compiling it in 2007r4 instead of r5.
>
> That's good to know. Thanks.
>
> Haven't gotten round to trying anything on Leopard yet as I've yet to
> order my new iMac, (so I can keep Tiger on the MacBook) but this is
> good to know all the same.
While that is certainly helpful when testing stuff yourself, it hardly
counts as a workaround for the problem. I can make it run an extra
hour before causing problems isn't exactly a feature I want on my
press release ;)
However, if there is something in the implementation that changed
between those versions it might point to a clue for RS to look into it
in more detail.
Haven't heard any more since Mars said they were looking into it, but
I'll take that for now.
Thanks,
James
James Sentman http://sentman.com
http://MacHomeAutomation.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|