I don't think Apple have introduced any new bugs or memory leaks
the last few years.
I _think_ that this is new on 7.2 on Mac, as our app now leaks big-
time - difficult to install old versions of QT to find out though.
The leak manifests itself as ~1MB leak of process memory per play-new-
clip in our app on 7.2. I'm having difficulty persuading QA that we
can release it in this state.
Duncan
public class QuicktimeLeakingTimersTest extends TestCase {
private static File FILE = new File("./testdata/
testclip.mov").getAbsoluteFile();
static {
if (!QTSession.isInitialized()) {
try {
QTSession.open();
} catch (QTException e) {
throw new RuntimeException("Could not initialize
Quicktime", e); //$NON-NLS-1$
}
}
}
private DataRef dataRef;
private Movie movie;
private Timer timer;
/**
* If we just create a movie and a timer on it, then both can be
disposed by gc
*
* Profiling shows that there are no instances of Movie or Timer
left
*/
public void testShowQuicktimeDoesReleaseNonActivatedTimers()
throws QTException {
movie = Movie.fromDataRef(dataRef, 0);
timer = new Timer(1, 1, null, movie);
checkCanDisposeMovieAndTimer();
}
/**
* If we just create a movie and a timer on it, then activate
the timer,
* neither can be disposed by gc, even when the timer is stopped.
*
* Profiling shows that the movie is held by the timer, which is
held by
* QTCallbackManagement, which is JNI global.
*/
public void testShowQuicktimeDoesNotReleaseActivatedTimers()
throws QTException {
movie = Movie.fromDataRef(dataRef, 0);
timer = new Timer(1, 1, null, movie);
timer.setActive(true);
_______________________________________________
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