Re: showing window causes EXC_BAD_ACCESS
Re: showing window causes EXC_BAD_ACCESS
- Subject: Re: showing window causes EXC_BAD_ACCESS
- From: "Michael Ash" <email@hidden>
- Date: Fri, 26 Sep 2008 00:07:12 -0400
On Thu, Sep 25, 2008 at 4:25 PM, Kyle Sluder
<email@hidden> wrote:
> On Thu, Sep 25, 2008 at 4:17 PM, Daniel Child <email@hidden> wrote:
>> If I press the button in question once, the window dutifully comes up. If I
>> close the window and press the button a second time, I get EXC_BAD_ACCESS.
>> Debugging, I found that both self and mLTableListingsWindow still exist.
>
> Sounds like your window is set to release when closed. Uncheck this
> box in Interface Builder.
Wandering slightly, but this makes me wonder, why does this flag
exist? I can't think of a single reasonable use case for it, and it
seems to cause no end to trouble to people who have somehow enabled it
without knowing it. It violates the memory management rules and makes
programs crash. Is there a good use case for it, or is it just some
sort of leftover?
Mike
_______________________________________________
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