• 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: showing window causes EXC_BAD_ACCESS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: showing window causes EXC_BAD_ACCESS


  • Subject: Re: showing window causes EXC_BAD_ACCESS
  • From: Scott Ribe <email@hidden>
  • Date: Sun, 28 Sep 2008 10:01:55 -0500
  • Thread-topic: showing window causes EXC_BAD_ACCESS

> Except that in every case I've seen of people getting bit by this, the
> window was still being implicitly retained by the nib's File's Owner.
> You should definitely *not* expect a top-level nib object to go away
> until File's Owner releases it.

Sure. The design intent here is that File's Owner is being dealloc'd, so the
window (along with all other top-level nib objects) should go away.

--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: showing window causes EXC_BAD_ACCESS
      • From: "Michael Ash" <email@hidden>
References: 
 >Re: showing window causes EXC_BAD_ACCESS (From: "Michael Ash" <email@hidden>)

  • Prev by Date: Re: Need to override +(Class) class?
  • Next by Date: Cocoa and "Reveal in Finder..."
  • Previous by thread: Re: showing window causes EXC_BAD_ACCESS
  • Next by thread: Re: showing window causes EXC_BAD_ACCESS
  • Index(es):
    • Date
    • Thread