[EMAIL PROTECTED] wrote: >> Dear Bob and Angel and others, >> >> >> What I have seen indicates that some portion of memory from "dead and >> gone" Jmols fails to be freed for reuse, and that this continues to >> add up throughout each browser session. The only way I know to free >> all the java memory for new molecular views is to close/quit the >> browser, thereby quitting java. When you start a new browser session, >> the memory is cleared. > > I tested this recently on MSIE/Windows, Firefox/Windows+Mac, > Opera/Windows, and all did a fine job of clearing memory for applets on > pages that had been closed. This is not something you can easily test for > yourself. If you can give me some test pages, I can look at it with tools > that I have. There was an issue dating way back to at least 10.0, but > 11.3.61 should have fixed that. >
Within a tutorial I would not expect that every new page will appear in a new window/tab by default but it will rather come up in the same one. And this might be handled differently than closing a window/tab with applet(s). And I think it should also be tested separately what happens if the same page with applet(s) is reloaded in the same window/tab. Regards, Rolf ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
