yade-dev team mailing list archive

[Bruno Chareyre <1273775@xxxxxxxxxxxxxxxxxx>]

Thanks for reporting. Could you check if the following replacement fix
the problem?

scene->interactions->requestErase(contact->getId1(),contact->getId2());
====>
scene->interactions->requestErase(contact);

I don't know if I failed some search/replace or if it has been commited
afterward, but the (id1,id2) form should not be used after [1] (two
years ago).

Even if it fixes your problem, please don't close the bug. It should be
simply impossible to write leaking code.  The mechanism of queuing
pending erase has been removed, but this nasty function filling the
queue are still there... my mistake.

Besides, you can't really erase interactions when they overlap. They
will effectively be created then reset at each step (but without the
memory leak). It would be better to not erase in terms  of performance.
Plus, I don't understand how you can decide to ignore them if you erase
them: history is lost, in the next iteration they look new.

Bruno

https://github.com/yade/trunk/commit/15182aca8473be86c74b139731dbb88b0007f759

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

Title:
  Too much memory used at creation/removal of interactions ? (JCFpm)

Status in Yet Another Dynamic Engine:
  New

Bug description:
  Hi,

  The problem is described here :
  https://answers.launchpad.net/yade/+question/242890

  I'm attaching the script describing this simple compression, with the
  .spheres file (in a 2d comment) that is loaded to "ymport" the sample.
  In this script/in the on-line yade version, the number of interactions
  that were requested to erase, despite a geometrical overlap, is not
  accessible.

  Let me know if I forgot something to let run the simulation.

  Jérôme

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