On Aug 10, 2011, at 3:12 PM, Quincey Morris wrote:

> Starting at the bottom, the last 3 show strong references to the window from 
> object 0x0000000400efa2e0. *That* object is being kept alive by 2 stack 
> references (#6 and #7), but it's a root reference in itself. I wouldn't be 
> surprised if this is the window controller.
> 
> You don't happen to have a singleton pattern of some kind for the window's 
> window controller? I mean something like [MyWindowController 
> sharedWindowController]. The simplest implementation of that pattern doesn't 
> ever release the singleton.

In my document class's -makeWindowControllers I'm setting a property to the 
window controller; could that be the problem?

(I'm only subclassing the window to override validateUserInterfaceItem: to stop 
performClose: at certain times.)
> 
> The first 4 roots are all stack references directly to the window.

Yep, I realise now they're related to code I put in to get the address.
> 
> The next step is to try getting the debugger to tell you the class of the 
> referencing objects -- 'po [0x0000000400efa2e0 class]', etc.
> 
> Note that the only root that *isn't* a stack variable is #5, so that's the 
> one I would be suspicious of. (After all, at a certain point, you'd expect 
> all the stack frames that might have a variable referring to a window to be 
> popped by the time you get back to the main event loop, so stack references 
> shouldn't really be what's keeping this alive, unless a reference to the 
> window has migrated up to a stack frame above the main event loop.)
> 
> If you get nowhere useful with the debugger, you can try following up in 
> Instruments (Allocations and Leaks). If a window gets leaked for every 
> document you open (but isn't detected by Instruments as a leak), then the 
> quickest way to get a picture of what's going on is to use heapshot analysis:
> 
>       
> http://www.friday.com/bbum/2010/10/17/when-is-a-leak-not-a-leak-using-heapshot-analysis-to-find-undesirable-memory-growth/

Thanks for the further ideas. I think ;-)

-- 
Shane Stanley <[email protected]>
'AppleScriptObjC Explored' <www.macosxautomation.com/applescript/apps/>

_______________________________________________

Cocoa-dev mailing list ([email protected])

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to