I have found a workaround for this bug in my application. If you explicitly call Canvas3D.stopRenderer(), it apparently releases whatever the resources that cause the Renderer thread to crash when you dispose of the Canvas3D in the user thread. At any rate, my app has stopped crashing when I close the window since I added this call to the finalize() method of my custom JComponent with a Canvas3D in it. Maybe others will find this fix helpful.
Regards, Mark Powell Jet Propulsion Laboratory Kelvin Chung writes: > > >Delivered-To: [EMAIL PROTECTED] > >MIME-Version: 1.0 > >Content-Transfer-Encoding: 7bit > >Date: Tue, 9 Oct 2001 16:37:31 -0700 > >From: Mark Powell <[EMAIL PROTECTED]> > >Subject: [JAVA3D] renderer.freeContext() crash outside VM > >To: [EMAIL PROTECTED] > > > >Hi, > >I am crashing outside the VM when I close the application frame with > >my Canvas3D in it. This is using JDK1.4 with Blackdown Java3D 1.2.1. > >I am running Red Hat Linux 7.1 with an NVidia Quadro 2 MXR video card > >and their latest drivers. I have attached the trace log. Please tell > >me that there is a workaround for this :) > > > >Thanks, > >Mark Powell > >Jet Propulsion Laboratory > > > > This is bug 4489714 - > JFTC:Multiple core dumps when Canvas3D removed and then added > > which is address in the upcoming v1.3 beta release. > > Thanks. > > - Kelvin > ------------- > Java 3D Team > Sun Microsystems Inc. > =========================================================================== 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".
