yade-dev team mailing list archive

[Václav Šmilauer <eu@xxxxxxxx>]

Hi there,

trying in Woo, I see some increase in the original Christian's script
adapted for Woo (it takes 3.5G RAM at the end), which is clearly an
issue, I don't see anything like that when re-assigning vertices to
Facets as Jan reported. Can someone reproduce that with Yade?

You should also check that there are no shared_ptr circles in Yade,
since those will be never de-allocated.

Cheers, vaclav

-- 
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1041084

Title:
  memory leak while erasing facets

Status in Yet Another Dynamic Engine:
  New

Bug description:
  I detected a memory leak in O.bodies.erase, when facets were erased (spheres are erased without memory leak!).
  In the attachment you will find two files, where you can reproduce the bug.

  1. Open a terminal with three tabs.
  2. Run top or htop in the first terminal tab
  3. In the second terminal tab run yade input file "memoryleak-erase-facets.py"
  4. Get the pid from first terminal tab (example 31667) and edit "get-memory-info.py"
  5. Run "python get-memory-info.py" in the third terminal tab and wait (ca. 5 min) to the end of the calculation.

  You will get an output file called "fig-memoryleak-erase-facets.png",
  where you can see the effect of the memoryleak.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1041084/+subscriptions