Re: [xmlvm-users] Releasing of CGBitmapContextRef / CGImageRef

[Paul P. <bay...@gm...>]

I believe the reason I commented out the "CFRelease" in CFType.finalize()
is that it was only there in the first place because of a bug in
UIGraphics.  Namely, popContext() was popping the context & then releasing
the current context, which is wrong & a different context altogether.  It
should've been releasing the context that was popped, so I fixed that.

Then, the bug in CFType.finalize() which called CFRelease could be fixed.
I.e. if it was left in there, it'd be incorrectly released twice.  Note
that CGContextRelease is equivalent to CFRelease.

Thanks,
Paul


On Tue, Jul 17, 2012 at 1:19 AM, Kensuke Matsuzaki <mat...@ki...>wrote:

> Hi,
>
> I had similar problem on CGContext, so I'm using '--xmlvm-new-ios-api' now.
> Rev 2118 commit comment says "Fixed UIGraphics.popContext() & removed the
> CFRelease in CFType's finalize".
>