Re: Workaround for framework leaks?
On Aug 15, 2010, at 15:35, Hans Larsen wrote:
> Override the init method IMP for this class, call the original init, check for releaseCount after init of
the border, release it if there's a problem. That might be the closest to a durable proof, and if it's fixed
should give you some time to release a minor version with the code removed.
> - written on a software keyboard
You should know that releaseCount says nothing. It doesn't count autorelease, and because it's private I
don't know even what the true net releaseCount should be. And removing the code in a minor release is not an
option, because it's not true that my users are using the same OS version that I do.
> On 2010-08-14, at 16:34, Christiaan Hofman <cmhofman@...> wrote:
>> On Aug 14, 2010, at 21:50, Gregory Weston wrote:
>>> Christiaan Hofman wrote:
>>>> I have found some leaks in the system frameworks. I know exactly what property is over-retained when a
new object of certain classes is created. Now my question is whether it is possible using this knowledge to
avoid this leak? I could imagine to just send a release to the property. However that may be dangerous,
because when Apple fixes the bug in the future that would lead to an over-release (and a crash). So would
there be some way to avoid that?