Using NSPureApplication, I get a large number of :
2005-05-03 08:34:00.847 java[11408] *** _NSAutoreleaseNoPool(): Object 0x35f370 of class NSImageCacheView autoreleased with no pool in place - just leaking
(2 per image instance to be exact) when the NSImage instance goes out of scope.
However, it seems that all the memory is reclaimed upon GC. Using the ActivityMonitor.app, I see both real and virtual memory end up ~where they started before entering the loop. Whereas not subclassing NSPureApplication, both the Real and virtual memory usage would just keep climbing until my system was choked.
So, while things *seem* to be working properly, I'm pretty spooked by the 'just leaking' messages.
Is there anyone from Apple listening ? Shed some light ?