I've been doing some work with java.awt.Images in the past few days
(1.2pre2 for glibc2.0, native threads, RH5.2), and I seem to be hitting
some strange deadlocks between my event and image-loading threads. As
best I can tell, it looks like ImageObserver.imageUpdate() is not being
reliably called while I'm waiting for an image to load.
I've been reading about these elusive threading problems delaying the
1.2 release... have they been known to assert themselves when dealing
with Images? (The real question for me: do I stare at my code and
scratch my head, or might I be able to blame the JVM or maybe the image
classlibs?)
Nathan Meyers
[EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
