Comments on: Simon says, MonoTouch downloading images like AppStore app in less than 50 lines with CoreAnimation Transitions!

By: Johnny Hughes

Johnny Hughes — Fri, 08 Jan 2010 02:05:31 +0000

Is there a way to manually dispose the necessary objects instead of using NSAutoreleasePool?

Also how are you finding the memory leak? I have a leak which i believe to be related to UIImage or it's inner CGImage but I'm not sure how to go about tracking it?

Johnny

By: Go iPhone

Go iPhone — Mon, 04 Jan 2010 18:39:31 +0000

Figured it out after digging into different posts. The answer is to wrap RequestImage() with using (NSAutoreleasePool pool = new NSAutoreleasePool())

The code looks like this now,
private void RequestImage(object state)
{
using (NSAutoreleasePool pool = new NSAutoreleasePool())
{

…

}
}

By: Go iPhone

Go iPhone — Mon, 04 Jan 2010 17:06:24 +0000

We just implemented image requests using the Simon's approach and both simulator and iPhone show "…class UIImage autoreleased with no pool in place – just leaking". I have tried to use NsAutoReleasePool to wrap the call but no success. Any suggestions?

Thanks

By: hemp

hemp — Tue, 03 Nov 2009 02:15:29 +0000

When you say "next version" do you mean 1.2 (currently Beta 1) or some future version that is not yet available?

By: Gonzalo

Gonzalo — Sun, 01 Nov 2009 16:55:07 +0000

I don't know if NsAutoReleasePool is required in Simon's case, but it won't be required in the next versin of MonoTouch since NSAutoReleasePoll will be dealt with in ThreadPool threads too.

By: Mike

Mike — Sat, 31 Oct 2009 14:03:20 +0000

Nice post!

Speculation -> does the NS* code in RequestImage leak in your example? I think you need to wrap it in an NSAutoReleasePool unless you're on the main thread, where mt handles it for you.

By: Johnny

Johnny — Fri, 30 Oct 2009 00:55:17 +0000

Thanks, this is outside the scope of threading, but can you please elaborate on the RefreshImage method and why you need to deal with the animation methods?