[SOLVED] RE: Determining unreleased objects after Quit
[SOLVED] RE: Determining unreleased objects after Quit
- Subject: [SOLVED] RE: Determining unreleased objects after Quit
- From: "Jon C. Munson II" <email@hidden>
- Date: Thu, 4 Dec 2008 11:04:58 -0500
- Organization: JTA Enterprises LLC
Just to close the thread...
This problem resolved itself. I didn't do nothing...
I suspect kaboshed bindings in a window/form.
Peace, Love, and Light,
Jon C. Munson II
"And Jesus looking upon them saith, With men it is impossible, but not with
God: for with God all things are possible." [Mark 10:27; KJV]
I sign "Peace, Love, and Light" for at least two reasons. First, it is my
truest desire for this planet and her people to live in Peace, with Love,
and in the Light of God. Second, to be an Ascended Master, one must Be. As
I wish to Be an Ascended Master (someday if not sooner), I must also Be -
thus I choose to Be Peace, Love, and Light as much as I can for everyone and
am therefore reflecting those thoughts to you.
-----Original Message-----
From: Joseph Kelly [mailto:email@hidden]
Sent: Wednesday, December 03, 2008 4:27 PM
To: email@hidden; cocoa dev
Subject: Re: Determining unreleased objects after Quit
On Dec 3, 2008, at 9:06 AM, Randall Meadows wrote:
> On Dec 3, 2008, at 9:38 AM, Jon C. Munson II wrote:
>
>> Namaste!
>>
>> In my application, when I choose File->Quit, the application
>> appears to
>> terminate. HOWEVER, it doesn't. SOMETHING(s) is(are) left
>> unreleased.
>>
>> Is there a handy way to determine what the object(s) is(are)?
>
> When your app quits, all of its memory used it released back to the
> system. However, your deallocs and such will NOT be called, since
> that would be a waste of time since everything's going to be
> released back to the system anyway. It's a shortcut, and usually is
> in your best interest.
>
> It can, however, bite you in certain situations, specifically non-
> memory resources that you need to do something with at termination.
> In my case, I needed to release access to a camera, so I had to do
> some of my cleanup work in -applicationWillTerminate:.
This is correct. I'm not sure exactly the mechanism -- and I suspect
it has something to do with Mach ports owned by the process which are
not shut down correctly -- but I've encountered a case where my app
appears "open" in the Dock, but does not appear in the bsd, Process
Manager, or Mach process lists. This only happens when the app
terminates abnormally, and our shutdown sequence does not execute.
I've also noticed that aborting a Debug session in Xcode 3.1.1 will
sometimes result in the app not quite going away, I presume also as a
result of having mach ports in a weird state.
Joe K.
_______________________________________________
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