Debugging a CALayer Bad Access
Debugging a CALayer Bad Access
- Subject: Debugging a CALayer Bad Access
- From: Gordon Apple <email@hidden>
- Date: Thu, 30 May 2013 12:40:03 -0500
- Thread-topic: Debugging a CALayer Bad Access
Title: Debugging a CALayer Bad Access
Debugging is not my strong suit. I usually rely on console messages, stack trace, logic, isolation, trial and error.
I have several types (nibs) of document windows, only one of which can be used at a time. Switching involves closing one and opening another. After realizing that the closed windows were not deallocating, I made sure all my iBOutlets were weak. The good news is that they now deallocate. The bad news is that they crash with “bad access” and no console messages. The windows all contain basically the same content. Their main view has a rather complex tree of CALayers, some custom, some not. The stack trace shows that during window deallocate, the bad access is on “actionForKey” for some layer. I overrode this (calling super) in the custom layers, but no joy in identifying the problem.
Is there a better way to trap this, so I can find out where it is coming from?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden