Other than the fact you're not checking for NULL when using
CFRelease(). I've learned to not trust any CF API to never return
NULL except CFSTR() (and I'm even hesitant on that).
But is this happening in another thread? It looks like this is a
cocoa application and if you're doing this in another thread, you
need to wrap the insides of the function with an NSAutoreleasePool,
much like almost anything at Jack in the Box.
No, it's a Carbon app - single thread (well, at the time this stuff
is happening it is) - and I've isolated it to RunStandardAlert(),
insofar as if I comment out that the problem goes away.
Cheers,
Richard
_______________________________________________
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
