Please see T14455. After cleaning most issues there, we still have a place in ImageStatisticsCalculator, which uses VTK Smart Pointers wrongly. Probably worth fixing.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | None | T14483 Wrong usage of vtkSmartPointer in mitk::ImageStatisticsCalculator | ||
| Resolved | None | T14455 Memory leaks from wrong usage of vtkSmartPointer |
Event Timeline
Comment Actions
New remote branch pushed: bug-14483-WrongVtkSmartPointerUsageImageStatisticsCalculator
Comment Actions
[57996d]: Merge branch 'bug-14483-WrongVtkSmartPointerUsageImageStatisticsCalcul
Merged commits:
2013-09-24 09:55:12 Michael Brehler [d68bd5]
Corrected SmartPointer usage
Comment Actions
[dcfd5c]: Merge branch 'bug-14483-WrongVtkSmartPointerUsageImageStatisticsCalcul
Merged commits:
2013-10-01 16:46:52 Michael Brehler [a01144]
COMP: Revert SmartPointerUsage because of test
Comment Actions
The test fail coming along with the proper smart point use goes back to the coupling of the vtkExporter's output bulk data to the internal image mask member of the ImageStatisticsCalculator via itkImporter. That is, after the exporter's deallocation through correct smart pointer reference counting, the member data is being allocated as well by the vtkExporter. The issue has been solved using a persistent image duplicate for the mask member.
Comment Actions
User norajitr has pushed new remote branch:
bug-14483-ImageStatisticsCalculatorVtkSmartPointerIssue
Comment Actions
(In reply to Tobias Norajitra from comment #5)
the member data is being allocated as well by the vtkExporter.
is being deallocated.
Comment Actions
[6bab0e]: Merge branch 'bug-14483-ImageStatisticsCalculatorVtkSmartPointerIssue'
Merged commits:
2014-02-12 16:23:37 Tobias Norajitra [c4989e]
Image mask member is assigned an image duplicate instead of the importer's output.