I've had a couple of replies already, so it would appear that this *is* a
genuine concern, although it may not just be related to Java 3D. I will run
some simple JRE2 based tested this AM and get back to the list with the
results. Lord only knows how I am going to work around this one...!

Daniel Selman
Tornado Labs Ltd.

Email:   [EMAIL PROTECTED]
Web:     www.tornadolabs.com
Phone:   +44 (0131) 343 2513
Fax:     +44 07070 800 483

Replies follow:

John Joseph Brecht [[EMAIL PROTECTED]]:

I had a similar problem.  It may not necessarily be a Java3D issue, but a
Plugin issue instead.  I had an applet (not a Java3D one though) that used
the
Plugin and was Runnable.  When I launched the HTML page containing the
applet
locally (as opposed to opening it from a server) the Plugin would keep it
alive
even after the browser was destroyed.  When I put it on a server (in fact it
was my own server on the same machine!) and called the HTML file by it's
URL,
the applet died just fine.

Use the plugin console and your task manager to see if the same thing is
happening with you.

If in fact, you find you have the same problem, we should consult the plugin
group.

Jake Russell [[EMAIL PROTECTED]]

I've seen Internet Explorer processes fail to die after closing the window
when they are viewing a Java3D applet (with java plug-in 1.2).  This is in
NT4 SP3 as well.  They must be manually killed.  Also Netscape on same
system can GPFault when closed as a Java3d applet is running with the
plug-in.

On Win '95 sometimes IE4 will just hang if it's opened directed to a
local-disk java3d applet page if MS Mail is open at the same time.  Not
sure what component's responsible though.

I hate to think what you must have found stress testing the system like
that (refresh 20 times, that is ;)  It looks like there may be some memory
or resource leaks here.  And they could very well be in the browsers, the
plug-in, java3d, or all of the above ;P





-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Daniel
Selman
Sent: 30 March 1999 00:26
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [java3d] Java 3D Applets and refresh


Action Listeners,

I posted a variant on this a while ago but it still has me stumped. When I
run a Java 3D applet on my system (NT 4SP3), for example HelloUniverse, it
runs fine. However if you close the browser (I've tried both IE4 and
Netscape 4) the process for the browser keeps running even though the window
is destroyed (and hence the whopping 20MB of memory is never released).

Additionally, if you press refresh (or reload) in the browser half a dozen
times or so the applet disappears (behind the Plugin?). I don't know if
these two are related. I have also seen similar results on Win98.

I'm hoping that my system is screwed up and our clients will never see this
(chance would be a fine thing!), so I'd really appreciate any feedback, both
the ability or inability to reproduce this.

Thanks again,

Daniel Selman

Tornado Labs Ltd.

Email:   [EMAIL PROTECTED]
Web:     www.tornadolabs.com
Phone:   +44 (0131) 343 2513
Fax:     +44 07070 800 483


=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 3D Home Page: http://java.sun.com/products/java-media/3D/


=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 3D Home Page: http://java.sun.com/products/java-media/3D/

Reply via email to