← Back to team overview

yade-dev team mailing list archive

Re: [Bug 1041084] Re: memory leak while erasing facets

 

2012/8/24 Christian Jakob <1041084@xxxxxxxxxxxxxxxxxx>:
> Message from syslogd@debian at Aug 24 10:56:01 ...
>  kernel:[1542691.744027] EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": NON-FATAL recoverable (Branch=0 DRAM-Bank=0 Buffer ID = 0 RDWR=Read RAS=0 CAS=0 NON-FATAL recoverable Err=0x2000 (FB-DIMM Configuration Write error on first attempt))

In this case the memory is blowing up, because you get an enormous number
of interactions (see the distance between facets).

Actually, the memory leakage will be also with spheres, not only facets, but
with spheres it will be not so quickly. I should say, this is a
"normal" behavior.

When you erase a body, you do not destroy it as an object. You just "erase" it
from the simulation, remove it from there. So the object is continuing to exist.

That is why you get an increasing of memory consumption, because you
create more and more body-objects.

Anton

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


References