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
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.
I don't know the specifics of your case as I don't use the
quicktime.app.time.Timer class. It's certainly possible this is a new
bug. Don't be afraid to try and solve it yourself though, using a
decompiler, memory profiler, etc.
I've certainly had to do things like call setMovie(null) or
disposeQTObject() myself before now to fix what I would class as bugs
in QTJava, but that's always been the case if you want a fix quickly,
even back in the days when Bill Stewart was actively working on it.
You might also consider using the underlying QTCallbacks directly
rather than going through the higher level app class, as that might
give you a bit of extra control over what's going on.
Square Box Systems Ltd
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