> On May 13, 2009, at 8:30 , Karan, Cem (Civ, ARL/CISD) wrote:
>
> > I have an object that I've turned into a singleton via the
> techniques
> > described at:
> >
> >
> http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/CocoaFundame
> > ntals/CocoaObjects/CocoaObjects.html#/
> > /apple_r
On May 13, 2009, at 8:30 , Karan, Cem (Civ, ARL/CISD) wrote:
I have an object that I've turned into a singleton via the
techniques described at:
http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/CocoaFundamentals/CocoaObjects/CocoaObjects.html#/
/apple_ref/doc/uid/TP40002974-CH4-SW3
Please ignore
the original question.
No ;-)
It is perfectly reasonable for a handful of objects to get allocated
and
never freed throughout the lifetime of a run. It is perfectly
reasonable for
some such objects to be instantiated lazily rather than at startup.
So it is
normal to have so
> Please ignore
> the original question.
No ;-)
It is perfectly reasonable for a handful of objects to get allocated and
never freed throughout the lifetime of a run. It is perfectly reasonable for
some such objects to be instantiated lazily rather than at startup. So it is
normal to have some
Answering my own question: it had nothing to do with my singleton, and
everything to do with over-releasing of objects that only showed up
when I had multiple threads running at the same time. Please ignore
the original question.
Thanks,
Cem Karan
__
I have an object that I've turned into a singleton via the techniques described
at:
http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/CocoaFundamentals/CocoaObjects/CocoaObjects.html#//apple_ref/doc/uid/TP40002974-CH4-SW32
This works great, but I've started debugging, and discovered that
