From: Bob Hanson <hansonr@st...> - 2007-06-12 03:37:34
Sérgio Ceroni da Silva wrote:
>I've been doing some testing regarding the problem where Jmol
>application freezes after a few changes in the default language.
>Apparently it's a memory matter. Every time the language is changed
>javaw uses more 6 to 15 MB. This happen with every language change until
>all resources are consumed. I hope this is not a java problem and a fix
>can be found.
This is a Jmol problem, but I am not experienced enough to solve it.
Language switching is not intended to be done more than once or twice in
a single Jmol run. If you have to switch back and forth among languages,
consider restarting Jmol. That's just the way it is for now. Perhaps
someone knows how to track down the memory leak associated with this; I
tried for some time, and I give up. The viewer is not finalizing upon
creation of a new one, which is what language switching involves. I do
not know how to fix that.
Get latest updates about Open Source Projects, Conferences and News.