I presume you have seen this in real code, not just this sample?
i.e Perhaps doing Drag Manager stuff outside of an eventLoop is bad.
Yes, and perhaps.
Perhaps the string is an autoreleased NSString that won't release
since there is no autorelease pool.
Does it still leak if you wrap an autorelease pool around your call
to DoLeaktest.
NSAutoreleasePool* pool = [[NSAutoreleasePool alloc] init];
DoLeakTest();
[pool release];
- still leaks.
Does it leak once per call to GetFlavorType, or just one object for
the lifetime of your app. I.e are you sure it isn't a cached string
in the drag manager
1 call = 16 bytes in 1 CFString block
10 calls = 144 bytes in 9 CFString blocks - go figure.
FYI - I find that ObjectAlloc is much better tool for CF/NS leak
detection than MallocDebug.
I will read up on that and try again.
Douglas.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
