0

Having a strange issue with my app where the entire iOS device gets locked up and the only thing I can do is restart the device. I am not seeing any exceptions getting thrown, nor am I seeing any memory leaks in Instruments.

The app has a navigation controller with a main menu. I then push a viewcontroller that has a grid of images being loaded. If I go back and forth between the main menu and the grid the app will crash after ~15 times. However, it isn't just the app that's killed, it's the entire OS which is something I've never seen.

At first I thought I was leaking memory, but Leaks isn't showing anything. I'm playing around with Allocations and I'm seeing that the grid view controller allocation count just keeps going up. The app is using ARC, which I don't like that much because it's too "magical", but I assumed it would be cleaning up properly.

One thing that concerns me is that viewDidUnload nor dealloc is being called on my grid view controller after it popped from the nav controller, so I'm never explicitly cleaning up my images or killing network connections. I assume this is where the issue is at but I don't know when I should kill these because the usual places to clean up (ie. viewDidUnload, dealloc) aren't being called.

This is happening on iPhone and iPad both running 5.1 and I'm using the AFNetworking UIImageView category to load images.

Cheers,

Meroon
  • 3,338
  • 3
  • 24
  • 29
  • You can try putting a [try/catch/log](http://stackoverflow.com/questions/8100054/no-exception-stack-trace-in-console-under-xcode-4-2-ios-5) function into your `main`. – Hot Licks Oct 04 '12 at 17:51
  • Your problem sounds like more of a deadlock situation. Look for the section you might be using locks (NSLock etc) or waiting for other thread to finish. Are you using CoreData or SQLite by any chance? – barley Oct 04 '12 at 18:19
  • I found the issue. Not sure why I didn't think of this earlier, but I was using CoreImage to do a vignette effect, and because the view controller wasn't being released, those CIImage objects were building up in memory. Not sure why this was flagged as a leak by Instruments. – Meroon Oct 04 '12 at 19:15
  • @barley: do you know if CoreImage uses locks? – Meroon Oct 04 '12 at 19:16

0 Answers0