Re: Diagnosing memory problems
Re: Diagnosing memory problems
- Subject: Re: Diagnosing memory problems
- From: Steve Mills <email@hidden>
- Date: Tue, 27 Nov 2018 23:42:30 -0600
> On Nov 27, 2018, at 16:56, Casey McDermott <email@hidden> wrote:
>
> Our main window has a tool bar across the top, an outline view on the left,
> and a tab view on the right. Choosing an item from the outline view fills a
> data entry screen into a new tab on the right.
>
> We started out using OS 10.11, but just switched to newer OS versions. 10.12
> has a couple display quirks but runs OK. In 10.13 and newer, switching tabs
> often crashes. It gives a warning about releasing a data entry field that is
> already released.
>
> In C++, we would diagnose this with a breakpoint in the destructor and then
> check the stack trace. But with ARC, a breakpoint at dealloc just shows
> performDelayedCleanup and then main. No clues to what's wrong.
Is the data on the right displayed via bindings? That can easily bite you if
things aren’t worked out the right way. Is the “data entry field” loaded
separately from a nib, and is the controller or owner actually owned by
anything? Thanks also a common mistake. It’s common to strong assign the
controller to the window, doc, or app delegate, whichever thing actually
instantiated it, so it will own it for its lifetime.
--
Steve Mills
Drummer, Mac geek
_______________________________________________
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