[EMAIL PROTECTED] wrote:
I'm trying to calculate the elapsed time by calling this twice and
getting the difference.
double Seconds()
{
return [[NSDate date] timeIntervalSince1970];
}
This is being called from an audio play back proc which is being
called
about 100 times a second. I'm getting this error message in the log
window a whole bunch of times.
2008-09-03 09:39:30.766 App[321] *** _NSAutoreleaseNoPool(): Object
0x36acd0 of class NSCFDate autoreleased with no pool in place - just
leaking
What I think is happening is that it's not being released fast enough.
Wouldn't it make more sense to believe that it's being autoreleased
without there being an established autorelease pool? You said you're
trying to call that routine, but you didn't say whence you were
trying to call it.
I was using AbsoluteToNanoseconds(UpTime()) but that's Carbon and that
won't work in 10.6.
Cough. I'm sure you didn't mean to just talk publicly about a product
under NDA. That said, it seems odd to suggest that something which
isn't even marked as deprecated today will cease functioning
wholesale in, oh, say, less than a year.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
