OK, Jmol 11.1.11 will have something for Henry Rzepa:
set echo top left
echo %{_memory}
You will see two numbers show up in that echo, and they will update
automatically as you rotate the model and such.
10.3/15.4
means Jmol is using 10.3 Mb of memory and has been allocated 15.4 Mb.
These are the numbers you want to monitor. Should the 10.3 hit the roof,
you will see that heap error. By seeing what this value is BEFORE such
an error, you can adjust your Java implementation to suit. Also, for
now, every time you load a new model you will see a message to the effect:
ZAP memory inuse, total, free, max: 835960 2031616 1195656 66650112
Read: 0.83 Mb in use, 2.0 Mb total allocated, giving 1.2 Mb free out of
a total Java max of 66 Mb. The last number may appear as "0" on some
installations.
That last number is what you should be able to tweak using the Java
control panel or something like that on your individual machine.
There is no memory leak.
Note that enlarging the window increases the memory use substantially.
So, a little smaller window may be a good solution if you are pushing
the limit. Anyway, now you have easy tools to monitor the situation. My
guess, Henry, is that you are using a very big screen and not allocating
enough memory to Jmol for that.
Bob
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
