I have a similar case where if I run my application too many times
successively it will eventually fail to run or hang. I believe it is some
kind of memory leak with respect to allocation of video ram. If you kill
the dos window you might be forcing it to flush some remnant memory?
-----Original Message-----
From: Discussion list for Java 3D API
[mailto:[EMAIL PROTECTED]]On Behalf Of Tim Bray
Sent: Monday, November 15, 1999 8:38 PM
To: [EMAIL PROTECTED]
Subject: [JAVA3D] A weird one that might get you
I have a moderately big & complex j3d app which, like all such, is a
first-rate memory hog. I'm developing on a Win/NT 4.0 workstation (SP4)
box, 550 MHz with a good card and lotsa RAM, so performance is adequate :).
I run the app in a command-prompt (ie DOS command line) window, by typing
java -Xmx96m arg arg arg arg arg....
Here's the problem: after I've done this two or three times, the java starts
up, finishes all its initializations (still lots of System.err.println()
calls
in there) and then, when it should render, just hangs. It sits there
burning CPU and doing nothing.
I can reliably fix this by killing the DOS window, opening another,
and running the exact same command. So... something in the cmd.exe
and java.exe combo is interacting toxically.
-Tim
===========================================================================
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".
===========================================================================
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".
