Hello, I just wanted to leave a short note on a possible bug I've observed. When I stop PyMOL from caching the geometry of my trajectory in RAM by set_defer_builds_mode, 3 and load a rather short trajectory (ca. 100 frames) of a protein that is shown in Cartoon-representation PyMOL starts eating my RAM gradually. As the trajectory loops several times more and more is stored to RAM, even worse the "reinit" command doesn't get rid of the cache, whatever is cached to RAM there... This doesn't seem to happen in lines-representation, but also for sticks. (PyMOL 1.5.0.4, Ubuntu 12.04 64-bit)
Regards, Daniel -- Daniel Mann, M.Sc Department of Biophysics Ruhr-University Bochum ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net) Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
