Thank you. But I did new tests, and the problem does not appear if in the
same pc I run the
same simulation, but using a single core, here is the top after 73 min, and
the memory
mantains its initial value.
Cpu(s): 53.2%us, 1.1%sy, 0.0%ni, 44.8%id, 0.0%wa, 0.3%hi, 0.5%si,
0.0%st
Mem: 2569
Hello,
the same happens to me on several computers, but it depends on the system.
I'm sorry I cannot dig the examples right now to add more precise information.
Could be shake? The system that fails is full of constraints.
Marcelo.
mdrun will not leak memory that badly. I would guess your outp
mdrun will not leak memory that badly. I would guess your output buffers
are not being flushed, so grow without bound.
Mark
On Oct 25, 2012 12:36 AM, "Pablo Serra" wrote:
> Dear users,
> I'm running a NVT simulation with gromacs 4.5.5,using
> the command:
>
> mdrun -nt $NSL
Dear users,
I'm running a NVT simulation with gromacs 4.5.5,using
the command:
mdrun -nt $NSLOTS
and the memory usage grows without bounds until a crash with the message
/opt/gridengine/default/spool/compute-0-8/job_scripts/1711: line 29: 25200
Killed /usr/local/bin/md
4 matches
Mail list logo