Skip to main content

1.3.2 issues

2 replies [Last post]
JavaFEA
Offline
Joined: 2006-02-17

I just gave a try at Java3d 1.3.2. Compared to 1.3.1, the picture is MUCH better for tracing boundaries of polygons with different colors than the interior of the polygon. For my application, this is critical.

The biggest problem is that 1.3.2 forced me to cut back memory usage by 200MBytes on my main Java application. Thus, of the 1.5GBytes on my PC, only 800 Mbytes is available for the application (CAD, so it needs a lot) compared to 1Gbyte before. This is just to open a 3d viewer with defaults. If I allocate too much for Java, opening a window generates this gem of a diagnostic:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x693f8c99, pid=3208, tid=2352
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0-b64 mixed mode)
# Problematic frame:
# C [atioglxx.dll+0x3f8c99]
#
# An error report file with more information is saved as hs_err_pid3208.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

This stuff unfortunately makes it very difficult for my application to be taken seriously by my customers!

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Alessandro Borges

Douglas,

some days ago we did a fine tunning on memory usage in our 3D application. This result in 3 bug fixes to Java3D (101, 102 and 103), and several small fixes in our main application.

I advice you to *NOT* use server JVM, use the latest 1.3.2 build, and use incremental garbage collector.

Alessandro

java3d-interest@javadesktop.org wrote:
I just gave a try at Java3d 1.3.2. Compared to 1.3.1, the picture is MUCH better for tracing boundaries of polygons with different colors than the interior of the polygon. For my application, this is critical.

The biggest problem is that 1.3.2 forced me to cut back memory usage by 200MBytes on my main Java application. Thus, of the 1.5GBytes on my PC, only 800 Mbytes is available for the application (CAD, so it needs a lot) compared to 1Gbyte before. This is just to open a 3d viewer with defaults. If I allocate too much for Java, opening a window generates this gem of a diagnostic:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x693f8c99, pid=3208, tid=2352
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0-b64 mixed mode)
# Problematic frame:
# C [atioglxx.dll+0x3f8c99]
#
# An error report file with more information is saved as hs_err_pid3208.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

This stuff unfortunately makes it very difficult for my application to be taken seriously by my customers!
---
[Message sent by forum member 'JavaFEA' (Douglas Stillman)]

http://www.javadesktop.org/forums/thread.jspa?messageID=59950™À

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

---------------------------------
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador do Yahoo! agora.
[att1.html]

scotthong
Offline
Joined: 2006-05-05

This issue might have something to do with ATI's driver
implementation. If you specify -Xmx maximum memory size
too close to the physical memory size, your will get the
exception as posted. However, this exception will only be
thrown when using Java3D with the ATI driver.

Java (Win32) requires continuous memory block and the
way ATI driver is implemneted allocating memory somethere
in the middle of the continuous memory block. This could
either prevent JavaVM from reserving enouch space or the
ATI's driver is unable to allocate memory because of it
is been reserved by the JavaVM. The latest ATI driver
seems to have resolved this issue together with Java3D
1.3.2. If you use nVidia's Video Card, there is no such
limitation.

You might want to try it on the latest ATI's driver or
using a nVidia video card to see if such issue still
exists. Anyway, ATI's OpenGL driver is not as good as
nVidia's and Java3D also brings in JNI components that
complicates the memory management issues.

-- Scott