• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Debugging a CALayer Bad Access
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging a CALayer Bad Access


  • Subject: Re: Debugging a CALayer Bad Access
  • From: Jens Alfke <email@hidden>
  • Date: Thu, 30 May 2013 11:42:12 -0700

On May 30, 2013, at 10:40 AM, Gordon Apple <email@hidden> wrote:

> 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.

Look up the docs for NSZombieEnabled. You can turn this on from the scheme settings in Xcode 4.

—Jens


 _______________________________________________
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


References: 
 >Debugging a CALayer Bad Access (From: Gordon Apple <email@hidden>)

  • Prev by Date: Re: Understanding Xcode build errors from using Objective-C runtime function in OS X's Foundation app template.
  • Next by Date: Re: Understanding Xcode build errors from using Objective-C runtime function in OS X's Foundation app template.
  • Previous by thread: Debugging a CALayer Bad Access
  • Next by thread: Re: Debugging a CALayer Bad Access
  • Index(es):
    • Date
    • Thread