From: Ashar Malik (
Date: Mon Feb 29 2016 - 15:24:14 CST

Since the number of frames are different on each load attempt, it appears
to be a memory issue (yes I know you said it isn't). Confirm this by
observing memory usage (in windows task manager)/as the trajectory loads.

I am not sure what you mean by visibility? Loading into memory is a task.
Viewing it is another and is not memory dependant.

If there are 2000 frames in your trajectory and you load with a stride of
10 --- then it really is a memory problem.
On Mar 1, 2016 8:50 AM, "Davit Hakobyan" <> wrote:

> Dear All,
> By now I was successfully loading XTC trajectory file containing 1500
> frames to VMD. Now as the simulation is still running and additional 500 ns
> were generated When trying to load the updated trajectory file containing
> 2000 frames VMD either crashes after loading some 1600 frames (if all the
> atoms are visible) or just stops randomly after loading 1623 ((the number
> can be different at different load attempts) frames (this is when only a
> selection like "resid 1" is active).
> Why I am basically sure that XTC file is correct is because when I try to
> load the same trajectory file with Stride 10, VMD then loads exactly 200
> frames.
> The XTC is generated on 64 bit Linux system and VMD is running on 64 bit
> Windows 7 with 12 GB of RAM, so memory is not a problem.
> The system size is ~74000 atoms.
> Does someone have any idea how to resolve this?
> Thanks a lot for any help.