Thanks Vaclav, Actually I don't see a difference between Yade and Woo regarding [1]. So I am puzzled... Also surprised by the fact that make_setter takes "return_by_value" [2], but clearly I need more boost-reading to really understand.
[2] make_setter(&thisClass::attr,py::return_value_policy<py::return_by_value>()) -- 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 assigning boost::python attributes 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 _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
