In my application I have some slider for controlling the rotation of an
object. So whenever a slider is moved, I set the transform for a
TransformGroup.

After dragging the slider around for a few seconds my application will lock
up. When I view the JVM state in a debugger the AWT-EventQueue thread is
stuck in a monitor wait in the method
"javax.media.j3d.MasterControl.runMonitor:2803":

I thought the Java3D API was thread safe; am I being clueless here and
supposed to do all of my scene graph updates from a specific thread (e.g.
SwingUtilities.invokeLater(Runnable))? Or could this possibly be a bug?


Version info:

Windows 2000, nVidia gForce 4 ti4400

java version "1.3.1_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode)

Java3D version "1.2.1_04 (OpenGL)".

Backtrace:

javax.media.j3d.MasterControl.runMonitor: 2803
javax.media.j3d.MasterControl.runMonitor: 2803
javax.media.j3d.MasterControl.runMonitor: 2803
javax.media.j3d.MasterControl.runMonitor: 2803

/**
 * @author Simeon H.K. Fitch
 * @organization Mustard Seed Software
 * @web http://www.mustardseedsoftware.com
 * @email [EMAIL PROTECTED]
 * @voice 210.867.1616
 * @fax 309.424.4982
 */

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to