Is there a way to avoid errors when releasing an object while code is still running?

Question

I have a UIView subclass that draws itself when -drawRect: is called. It only takes a moment, but under extreme circumstances, such as low memory and deletion of the instance when going to another view controller, the draw function doesn't complete before the the object is deallocated.

How am I supposed to deal with this issue? The deallocation causes any calls to [self ...] to throw a EXC_BAD_ACCESS, which the drawing function does to determine how to draw itself.

Note:

I'm largely using the framework to handle memory management. The issue lies in the asynchronous calls to -drawRect: from the CATiledLayer that the UIView uses, which come in before the UIView is released. However, since it's asynchronous, the -didReceiveMemoryWarning runs while it's drawing, causing the view to be released in the middle of the drawing.

Answer 1

Start by reading Apple's Memory Management Rules:

Cocoa Memory Management Rules

The bottom line: the way to "deal" with the issue is to make sure you manage your objects and their memory use properly. A crash because of a deallocation is not something to be trapped but a flat-out bug in your app that needs fixed.

Answer 2

I think the answer here is: use @synchronized