Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
Re: Memory Leak with Active Timer
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory Leak with Active Timer



Thanks Rolf, believe me I have been trying to solve it myself (62 hours in the last week and counting :-( That's the gist of my plea to at least release the source so that we can support ourselves.

disposeQTObject is our usual tactic, but right now that blows up our VM on Mac. We've resorted to a queued disposer, where we wait 10s after we've finished with any QTObject's before actually disposing of them, with the termination lock taken around batches (a Movie and its MovieController), and still I can't click-play more than 200 times without crashing, usually somewhere in QuickDraw - RegnRect or something like that.

I think we're going to have to give up on the callbacks altogether and just observe changes with a Swing Timer, that is, if we don't give up on QTJ altogether.

We must do that lunch

Duncan

On 3 Nov 2007, at 09:44, Rolf Howarth wrote:

At 07:53 +0000 3/11/07, Duncan McGregor wrote:
On 2 Nov 2007, at 23:40, Rolf Howarth wrote:

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

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.

-Rolf
--
Rolf Howarth
Square Box Systems Ltd
Warwick, UK.
http://www.squarebox.co.uk

_______________________________________________ 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
References: 
 >Re: Three New QT Documents Available (From: "email@hidden" <email@hidden>)
 >Re: Three New QT Documents Available (From: Rolf Howarth <email@hidden>)
 >Memory Leak with Active Timer (From: Duncan McGregor <email@hidden>)
 >Re: Memory Leak with Active Timer (From: Rolf Howarth <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2011 Apple Inc. All rights reserved.