From: Axel Kohlmeyer (
Date: Fri Nov 25 2011 - 09:38:01 CST


it looks like you have saved the state after
having worked with a huge number of molecules.
it is quite possible, that you have triggered some
internal and hard to track down VMD bug.

i see two things that you can do:
a) launch VMD with -debug and then trigger
the "hang" again and then do a kill -STOP
to the "stuck" VMD process and try to get
a stack trace so that we get an idea what
is going on.

b) use a text editor to trim off all the useless
script code. a saved state usually is very verbose
but for the most part, the script code produced
is identical with the default, so it would not really
be needed. that is particularly true for the color
table settings. with such a lean and mean state,
you may not run into any problems.


On Fri, Nov 25, 2011 at 1:51 AM, Bjoern Olausson
<> wrote:
> Hi,
> I generated some representations via a script and saved the view with
> "save_state" command.
> When i load this state file, VMD reads it, does everything what I expect it to
> do, shows the final representation as expected, but then VMD is unresponsive
> has 100% CPU usage and all VMD related window, except the cmd, are neither
> updated nor usable. I have to kill the VMD process..
> I am running VMD 1.9 on Linux 3.0.6 with 8GB RAM, a GeForce 8600 GT and a
> Core2 Quad CPU Q9300 - composing is disabled for KDE.
> You can find the state file here:
> An here's the output of VMD when reading this file (vmd -e statfile.vmd):
> Any ideas?
> Cheers,
> Bjoern
> --
> Bjoern Olausson
> Martin-Luther-Universität Halle-Wittenberg
> Institut für Pharmazie
> Wolfgang-Langenbeck-Str.4
> 06120 Halle/Saale
> Phone: +49-345-55-25122

Dr. Axel Kohlmeyer
College of Science and Technology
Temple University, Philadelphia PA, USA.