> I'm worried that Jmol or Java is not properly dealing with memory > allocation, specifically DEallocating memory after large molecules are > replaced by small ones. What am I missing here?
Java does not have any memory leakage problems. Jmol might ... but only if you can reproduce it in the Jmol application. Memory never gets returned to the OS. So, from the perspective of the OS it is a one-way valve. You need other tools to determine how much memory is available in the Java heap. LiveConnect surely complicates things considerably. Speculation ... If you reference Java objects from JavaScript then they might never release that reference. That is, the LiveConnect *might* hold onto the reference as long as you are on a page (or forever) because it might not be tied in with the JavaScript garbage collector and therefore the easiest solution would be to make the references 'permanent'. Miguel ------------------------------------------------------- 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&kid0709&bid&3057&dat1642 _______________________________________________ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
