| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0013409 | VTK | (No Category) | public | 2012-08-29 19:34 | 2012-09-06 19:00 | ||||
| Reporter | David Gobbi | ||||||||
| Assigned To | David Gobbi | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 5.10.0 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0013409: Python memory leak for observers | ||||||||
| Description | The PyVTKObject does not check for reference cycles in its observers, even for things as simple as an observer that is a method of the object itself. The place for the checks to be performed is PyVTKObject_Traverse, which can check each observer to see if it is a vtkPythonCommand, and if so, traverse its "obj" member which is a python object. This will allow simple reference cycles to be broken. More complex reference cycles would require a special vtkPythonGarbageCollector class that could use VTK's ReportReferences function to traverse VTK's reference tree, looking for python objects. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | TBD | ||||||||
| Type | performance | ||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0029139) David Gobbi (developer) 2012-09-06 19:00 |
Committed patch 0ed9cde3 to fix this bug, prior to VTK 6 release. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2012-08-29 19:34 | David Gobbi | New Issue | |
| 2012-08-29 19:34 | David Gobbi | Status | backlog => tabled |
| 2012-08-29 19:34 | David Gobbi | Assigned To | => David Gobbi |
| 2012-09-06 19:00 | David Gobbi | Note Added: 0029139 | |
| 2012-09-06 19:00 | David Gobbi | Status | tabled => closed |
| 2012-09-06 19:00 | David Gobbi | Resolution | open => fixed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |