>Delivered-To: [EMAIL PROTECTED]
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
>Date: Tue, 18 Sep 2001 19:09:14 -0700
>From: "Michael P. McCutcheon" <[EMAIL PROTECTED]>
>Subject: [JAVA3D] JDK 1.4 beta 2 performance
>To: [EMAIL PROTECTED]
>
>Anyone notice that 1.4 b2 seems to exhibit 'choppier' behavior with Java3d
>1.2.1_002 than 1.3.1?
>
>I've been fooling around with it and it seems to be a little slower.
>Running with -server mode is unuseable (as expected).  Running with -client
>mode performs about the same as 1.3.1 but is choppier.  I turn on
>the -verbosegc flag and it appears garbage collection is NOT the problem
>because (in my program) GC hardly ever happens...but there are still
>noticeable pauses (although very slight)...it's just not as smooth as it was
>with 1.3.1.
>
>Anyone know if there are any issues with 1.4 and Java3d?
>
>Also, I get the following upon startup:
>
>wglCreateContext Failed: The handle is invalid.
>
>wglMakeCurrent Failed: The handle is invalid.
>
>Know what this means?
>

The performance (and memory leak) problem is JDK1.4 bug
4470749 - Java3D fail to initialize underlying OGL/D3D library in jdk1.4
sometimes

which is fixed in the next JDK1.4 release.

The startup problem is Java3D bug which is not compatible with
JDK1.4, it will be fixed in the next java3d patch release.

- 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".

Reply via email to