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
On Dec 13, 2007, at 9:43 AM, [EMAIL PROTECTED]
wrote:
Message: 3
Date: Thu, 13 Dec 2007 14:56:34 +0100
From: Rolf Huehne <[EMAIL PROTECTED]>
Subject: Re: [Jmol-users] Exploring the limits
Timothy Driscoll wrote:
On Dec 13, 2007, at 6:28 AM, Rolf Huehne wrote:
Because an "OUT OF MEMORY" error freezes Jmol and the standard user
most
...
The problem with this is that there is no "standard java memory
allocation". In my experience it differs largely between operating
systems and also between Java versions.
Another problem is that even if you could apply some rule of thumb
(e.g.: 20 times uncompressed file size + minimum requirement for the
applet) this would only apply if a single applet was started.
But I would rather expect that often a user will explore several
structures one after the other. And unfortunately the memory of
applets
whose window/tab was closed it not always released.
Another problem is the applet size. Since the user can set the size
freely this might also drastically change the memory required.
So I would really prefer a more situation-specific solution.
Regards,
Rolf
-------------------------------------------------------------------------
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
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
