Operating system: Windows 10
Slicer version: Slicer 4.11.0
Expected behavior:
Actual behavior:
When I exit the Slicer, something wrong happened. please check the screenshot below.
Operating system: Windows 10
Slicer version: Slicer 4.11.0
Expected behavior:
Actual behavior:
When I exit the Slicer, something wrong happened. please check the screenshot below.
Hi, thanks for the report. Please add what steps led to this (what extensions were installed, what operations you performed). Generally memory leaks like this aren’t harmful but we’d like to clean them up.
The first listed object that you haven’t released from memory is a vtkCollection
, which usually indicates that you have forgot to call UnRegister
for a collection returned by a factory method, such as slicer.mrmlScene.GetNodesByClass
.
See these pages for more information:
Deleting unknown object
error might indicate that something wrong with how the VTK object is constructed. Make sure you follow example of other MRML nodes exactly (e.g., you use vtkStandardNewMacro
to implement New()
method).
Hello Steve,
The problem has been solved after delete one extenson.
Thank you very much.
Hello Andras,
The problem has been solved after delete one extenson.
Thank you very much.