Chris Abbey wrote:
>
> Glenn's applet, while it functions fine while running, after quiting seems
> to leave some nasty trails in the JVM which are chewing up memory, as well
> as pitching expections around like crazy. Netscape's pathetic JVM just
> can't handle that. Looks like your network thread is still alive and trying
> to dispatch events into the AWT threads... but they die a quick death
> because everything got cleaned up... at least that's what it looks like
> from the couple thread breaks I took. Run it in applet viewer with
> verbosegc and you'll see it sits fine while it's running, but as soon as
> you choose quit the jvm starts gcing a lot.
Thanks! I'll have to work on this one. I see the error that I need to mend.
> Otherwise Glenn, your applets worked fine in NS Comm 4.61 and appletviewer
> from the "IBM Developer Kit for Windows(R), Java(TM) Technology Edition,
> Version 1.1.7." (one more reason lawyers and engineers shouldn't mingle).
>
> As for the MAC and IE issues... IE 5 does not support Java; and the last
> JVM I saw on the Mac (addmitedly a long time ago) was still in the 1.0 AWT
> event model....
Wow! I did'nt know Billy G was going to be an ass about this Java battle and
leave it out of IE5. Maybe with this info, I will be able to convince several
of my freinds to dump IE5 and switch to Netscape.
Thanks again!
--
Glenn Valenta Engineering @ http://www.coloradostudios.com
[EMAIL PROTECTED] http://ouray.cudenver.edu/~gavalent/
[EMAIL PROTECTED] Personal mail
[EMAIL PROTECTED] Work mail
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
