I think the reason we didn't have this in the first place is that it could cause memory leaks since it doesn't also delete the object. Group however shouldn't delete the object, since the object might be used elsewhere. Doing it as specified in the patch would require that the programmer understand it's not really deleting the object and so they would need to do so themselves. The problem with that is that programmers might not realize that is the case. I'm not sure what the best way to handle this is, so I'm not saying this patch is good or bad. I just wanted to point out this possible problem. What do other people think should be done? Should we do it as this patch describes? Are there better ways to do it?
Thiago
Li-Ta Lo wrote:
Hi,
Can someone add this into the official tree? I am generating
and deleting Manta objects from VTK dynamically. It creates
memory leak if I can't remove old objects from the world group.
Boonth,
This is patch is what you need for the current vtkManta.
Ollie
Archive powered by MHonArc 2.6.16.