Good to know I'm not the only one.... bad to know that they still don't seem to be resolving it very quickly. In terms of cleaning up, I have tried many things.
1) I have tried disposing of objects as I am finished with them and just before I null out the last remaining pointer to the object
2) I have tried allowing GC to dispose of them 3) I have tried forcing GC to finalize and clean up memory on a routine basis when *zero* calls are being made into quicktime. 4) I have tried using the QTUtils.reclaimMemory
() call to force quicktime to reclaim memory at various "safe" points 5) I have tried removing my dependence on a DrawComplete callback 6) I have tried detatching the draw complete handlers manually before disposing of the quicktime objects
This list could go on many many times over as I have tried just about every imaginable code combination to prevent Quicktime from crashing. The only thing right now that I can think of that I haven't tried is to use a QTComponent instead of a QTJComponent (I do have a good reason to be using the JComponent).
The other thing that I was going to try but don't expect to show any benefit is to lock all quicktime calls inside a synchronization on the finalize lock from QTSession. The other person I am working with seems to think that this is the same "random" crash that people are complaining about there but I beg to differ. I already synchronize all of my threads on each individual movie so that no 2 threads are working on the same movie at the same time. The only exception of course is the TaskAllMovies thread.
Oh you beauty, I was beginning to think it was my fault.
We have a very similar crash, although I usually see either thread 0 or
another crash around v2m_PurgeScheduleQueueContents, with MediaMoviesTask in the stack.
It may or may not have been introduced with QT 7.2, and is still present in QT 7.3.
I've sent logs to developer support, but I'm afraid that they don't seem to
be finding a fix in a hurry.
PS - when you say everything is cleaned up, do you disposeQTObject, or let GC deal with it?
Original Message: ----------------- From: Ben Thompson
email@hidden Date: Thu, 8 Nov 2007 01:03:32 -0600 To: email@hidden Subject: SetMovieRate crash
Has anybody else experienced a crash where after playing back a number of movie files eventually the application simply crashes with a BAD_ACCESS error and the thread that crashes has a stack trace similar to the
following? This has been plaguing me for the last few days and I have tried almost everything I can think of to locate and resolve this crash. It occurs *significantly* less with sorenson compressed video clips than with
h.264 compressed video.
In a nutshell, I pretty much do the following repeatedly (approximately once every 2-3s): 1) load a movie file 2) create a movie player 3) create a QTJComponent 4) set the play rate of the movie player to the preferred play rate of the
movie file 5) schedule another thread to stop the movie after a specific amount of time has elapsed 6) ... 7) movie is stopped 8) everything is cleaned up 9) repeat
Do not post admin requests to the list. They will be ignored.
QuickTime-java mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden