[Openmcl-devel] cocoa bridge memory management changes?
Willem Rein Oudshoorn
woudshoo at xs4all.nl
Fri Sep 24 13:45:44 PDT 2010
Raffael Cavallaro <raffaelcavallaro at mac.com> writes:
> On Sep 24, 2010, at 4:02 PM, Willem Rein Oudshoorn wrote:
> There appears to be another recently introduced bug in make-instance
> which doesn't lead to a crash, but does lead to a memory leak. I can
> tell this because when I do object allocation by (for example):
> (make-instance 'ns:ns-data :with-contents-of-file ...
> I get a memory leak, but if I do the same exact thing by calling:
> (#/dataWithContentsOfFile: ns:ns-data ...
> I don't.
Hm, but these two things are NOT the exact same thing. So, I assume you
are saying that:
(setf *i* (make-instance 'ns:ns-data :with-contents-of-file))
does leak, but
(setf *i* (#/dataWithContentsOfFile: ns:ns-data ..))
does not leak.
More information about the Openmcl-devel