I am using ns-3 on windows using VS2017, I have to repeat the simulation several times with different seed numbers. I created a ns-3 script that runs and destroys the simulation after. The problem is that the visual studio does not reset the memory used, after the execution of (Simulator::Destroy()), the memory consumed, shown by the diagnostic tool, stays the same and increase with the next repeated simulation?
Does anyone have the same problem?
Aucun commentaire:
Enregistrer un commentaire