The 10.4 and above call [pool drain] is essentially the same as [pool
release]. Probably the drain call was added because in the new
garbage collected world of ObjC 2.0 a call to release is a no-op.
You could implement a category on NSAutoreleasePool that simply
called release and it should work for pre-10.4 code.
-Barry
On Jul 23, 2007, at 5:20 AM, Luc Heinrich wrote:
Greetings,
I'm getting reports from users running my application (the Miro
player if you happen to know it) on OS X 10.3.9, that they are
getting constant crashes since they upgraded to Quicktime 7.2. I
did some tests myself and I can consistently reproduce the crashes.
FWIW, Miro is a PyObjC application, using QTKit to provide movie
playback.
The crash is occuring when trying to "extract" a single frame from
a movie file using the QTMovie 'frameImageAtTime:' method. I'm
getting this in the console:
NSThread: ignoring exception 'NSInvalidArgumentException' (reason
'*** -[NSAutoreleasePool drain]: selector not recognized') that
raised during delayed perform of target 0x7d87ae0 and selector
'performAndNotify:'
Which of course doesn't say much...
So in short:
- OS X 10.3.9 + QT 7.1.6: frameImageAtTime succeeds
- OS X 10.3.9 + QT 7.2: frameImageAtTime crashes
- OS X 10.4.10 + QT 7.2: frameImageAtTime succeeds
I haven't seen any mention of this problem anywhere besides the
whole CFM disaster. Is this another known problem ?
--
Luc Heinrich
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
