Details
[I am performing an MD simulation with LCAO of a silicate melt (SiO₂) system with ~324 atoms. The calculation is running on a single node with 128 CPU cores and 256 GB memory. The version is abacus-develop.
The simulation starts normally, but after about one hour (~37 MD steps), it crashes due to memory exhaustion.
Since the job runs fine at the beginning and only fails after several MD steps, it seems that memory usage is increasing during the simulation rather than being a static memory limitation.
I would like to ask:
Could this behavior be related to a compilation issue (e.g., MPI / ELPA / ScaLAPACK / memory handling)?
Is there any known issue of memory accumulation or memory leak in MD simulations (especially with LCAO)?
What is the recommended way to solve it in this case?]
SiO2.zip
Task list for Issue attackers (only for developers)
Details
[I am performing an MD simulation with LCAO of a silicate melt (SiO₂) system with ~324 atoms. The calculation is running on a single node with 128 CPU cores and 256 GB memory. The version is abacus-develop.
The simulation starts normally, but after about one hour (~37 MD steps), it crashes due to memory exhaustion.
Since the job runs fine at the beginning and only fails after several MD steps, it seems that memory usage is increasing during the simulation rather than being a static memory limitation.
I would like to ask:
Could this behavior be related to a compilation issue (e.g., MPI / ELPA / ScaLAPACK / memory handling)?
Is there any known issue of memory accumulation or memory leak in MD simulations (especially with LCAO)?
What is the recommended way to solve it in this case?]
SiO2.zip
Task list for Issue attackers (only for developers)