>>Sérgio Ceroni da Silva wrote: >> >>Dear all >>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. >>Regards >>Sérgio >> > >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. > >Bob
Hi Bob, thanks for your reply. I've come across this problem while checking the pt_br translation I did. I was going from en to pt_br and back again several times to make sure the translation was meaningful and not just literal. Sure no sane person will change languages more than a couple of times, so it is not a big problem. I've reported it just because I thought this memory leak could be a symptom of a more important problem. Thanks again. Sérgio ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
