Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Exception at WinNativeHelper under Windows

This is something thats been around for a while but I havent had a reproducible case with me, but this is something I need to look into , finalizer is been invoked on the DrawingSurface, this should not happen until you quit the application or remove the canvas from the window. I need to see whats going on with this...

thanks
anant

On Friday, February 28, 2003, at 05:12 AM, dean perry wrote:

(re 1.4.1 on Windows QTJ crashes)

On Friday, Feb 28, 2003, at 08:17 Australia/Melbourne, Rolf Howarth wrote:

Very interesting, and very well timed! I've just started seeing this in my code when running under Virtual PC. Sometimes it's fine, sometimes it crashes consistently. From the look of the stack trace, there seems to be a race state and it all depends on how lucky or unlucky you are regarding when the JVM finalizer thread happens to > run.

count me unlucky. I have heaps of issues - even on startup - and there's nothing much allocated at that point to be marked as GC'ed - besides which a lot of profiling has me mostly reusing objects now rather than re-allocated and leaving it to the GC to clean up.

I've regressed to 1.3.1 and am seeing heaps fewer crashes (that aren't in my stuff ;-)


This is similar, but not the same, as another problem I've recently experienced under OS X. I've been getting very infrequent random crashes when doing certain heavy QTJava processing, which I'm almost certain is due to the garbage collector kicking in and disposing some QT objects. QuickTime isn't re-entrant and a crash can occur if QTObject.finalize() is called while another thread is invoking QuickTime. I fixed my particular problem by enclosing the entire process in

synchronized(QTSession.terminationLock())
{
...
}

This has the disadvantage of blocking any QT objects from being freed up in that block so you may need to take care if you're allocating lots of things. I can't know 100% for sure but I haven't had any random crashes since then :-)

this is interesting - but how the hell do you implement it? - are you blocking in main() waiting on something in your app finishing?

I mean you can't just do:

synchronized(...)
{
myWindow.show();
}

because it'll exit immediately and start living off the event thread...

has anyone come up with a 100% reproducible example?

(Hey Anant, I know you're busy right now - but any clues from inside the box where to look to nail this)

cheers,

dean perry
abstract plane pty. ltd.
_______________________________________________
quicktime-java mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/quicktime-java
Do not post admin requests to the list. They will be ignored.
_______________________________________________
quicktime-java mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/quicktime-java
Do not post admin requests to the list. They will be ignored.


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

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.