> For reasons I don't > recall at the moment, pymol uses more memory with a pse file than with > the same objects loaded through a script (you could check the list > archives for more details if you're curious).
Just FYI: This is an unfortunate unavoidable consequence of the fact that we use Python's portable, platform-independent "pickle" machinery for PyMOL session files. Packing or unpacking a Session or Scene file thus requires that there be two simultanous copies of the information to reside in RAM simultaneously: one native and a second in Python itself. So when memory is a limiting factor, we definitely recommend using scripts instead of sessions. > > > PyMOL simply crashes under Windows Vista Home Premium as well as under > > Ubuntu Linux v8.04 LTS without error report. My dual OS system is a > > Not sure about windows, but with linux you should get some level of > messages by launching from a command prompt instead of an icon. If > you're running out of memory, you'll get a core dump message (at least, > that the usual symptom on my systems. > You might want to have top running in a different terminal so watch how > much memory pymol is trying to use (or is able to use before crashing). Correct -- To get those same console messages on Windows, you need to launch PyMOLWin.exe from a Windows command line with the "+2" option to prevent PyMOL from hiding the console window: (start menu -> run -> cmd [return]) cd c:\program files\delano scientific\pymol pymolwin + 2
