[Openmcl-devel] cocoa bridge memory management changes?

Willem Rein Oudshoorn woudshoo at xs4all.nl
Fri Sep 24 03:18:52 PDT 2010

Raffael Cavallaro <raffaelcavallaro at mac.com> writes:

> To be specific, I have a custom NSView subclass with some :id slots,
> and I'd been calling #/release on them in the parent window's #/close
> method, which worked fine.

I don't know if the objective-C bridge memory management is changed in
any significant way.  However, what you describe above sounds slightly
odd to me.    Why would you send a #/release on :id slots in a custom
view from the NSWindow?  

> Now, I get no errors or console warnings,
> but the memory is not being reclaimed.

Memory for which objects?  If it is the :id slots you could try to see
with #/retainCount if they are supposed to be deallocated 
(However note that #/retainCount can give a very misleading picture 
if #/autorelease is called on the instance and the pool is not emptied

Wim Oudshoorn.

More information about the Openmcl-devel mailing list