yade-dev team mailing list archive

[Anton Gladky <1041084@xxxxxxxxxxxxxxxxxx>]

I am afraid, we can nothing to do with that.
Yade itself does not "work" itself in this example.

Anton


2012/8/30 Jan Stránský <honzik.stransky@xxxxxxxxx>:
> The problem could be linked to this example:
>
> f = utils.facet(((1,0,0),(0,1,0),(0,0,1)))
> n = 100000000
> for i in xrange(n):
>   f.shape.vertices = Vector3(1,0,0),Vector3(0,1,0),Vector3(0,0,1)
>
> that also leads to memory leaks, while it should not..

-- 
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