I've been seeing the exact same thing on WindowsXP/Firefox2.0/Java1.6. The memory used creeps up after each reload, and then I need to restart.
Noel > From: Craig T Martin <[EMAIL PROTECTED]> > Subject: Re: [Jmol-users] Jmol-users Digest, Vol 19, Issue 21 > To: [email protected] > Cc: Rolf Huehne <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > While we're talking memory allocation, and with respect to: > > "And unfortunately the memory of applets whose window/tab was closed > it not always release " > > For the stuff that I'm doing, I've known for some time that after > loading (and closing) various windows, Jmol eventually stops working > (Jmol, not the browser, hangs on a subsequent load) and I have to > restart the browser. This on a Mac running either Safari or FireFox > (latest everything, but it's been happening for more than a year). If > I look at the memory allocated to Safari, for example, I can see a > step increase on every new Jmol applet. So it is clearly not > releasing memory. > > I think I've seen this discussed here before, but with no real > answer. Is there a way to insure that when an applet closes, it > releases its memory? Or is there a way to manually do so? Is this > just a problem for me or do others see this? Perhaps I'm doing some > sort of call wrong? > > An implementation is at: > <http://www.chem.umass.edu/people/cmartin/Jmol/WingedHelixII> > > You need to open and close maybe a half dozen times to see the effect. > > Thanks, > > Craig > ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
