<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=SK link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>try building vtk with VTK_DEBUG_LEAKS enabled and then you can use vtkDebugLeaks class PrintCurrentLeaks method to print all existing vtk objects. Here you can see whether the object count is increasing or decreasing<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Elvis Stansvik [mailto:elvis.stansvik@orexplore.com] <br><b>Sent:</b> Thursday, September 1, 2016 9:05 AM<br><b>To:</b> RobertS <spir.robert@gmail.com><br><b>Cc:</b> VTK Users <vtkusers@vtk.org><br><b>Subject:</b> Re: [vtkusers] Memory not released when volumes are removed<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>2016-08-31 17:51 GMT+02:00 Elvis Stansvik <<a href="mailto:elvis.stansvik@orexplore.com" target="_blank">elvis.stansvik@orexplore.com</a>>:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p>HI Robert, <o:p></o:p></p><p>Den 31 aug. 2016 5:30 em skrev "Róbert Špir" <<a href="mailto:spir.robert@gmail.com" target="_blank">spir.robert@gmail.com</a>>:<br>><br>> Hi Elvis,<br>><br>> I noticed the same behavior before ( here is the topic <a href="http://vtk.1045678.n5.nabble.com/memory-leak-in-vtkStructuredPoints-or-am-I-doing-something-wrong-tt5738805.html" target="_blank">http://vtk.1045678.n5.nabble.com/memory-leak-in-vtkStructuredPoints-or-am-I-doing-something-wrong-tt5738805.html</a> )<br>><br>> Looks like it is the standard behavior of Linux (although very weird), since this is not happening in Windows or OS X.<o:p></o:p></p><p>Ah right, now I remember your post. I'll do some more testing to verify that this is actually what's happening in my case, but it likely is.<o:p></o:p></p></blockquote><div><p class=MsoNormal style='margin-bottom:12.0pt'>I don't think this is the phenomenon I'm seeing. I tried opening the same dataset repeatedly in my app, and I got:<br><br>77 MB<br>368 MB<br>633 MB<br>860 MB<br>1003 MB<br>1171 MB<br>1345 MB<br>1518 MB<br>1691 MB<br>1858 MB<br>2029 MB<br>2201 MB<br>2371 MB<br>2543 MB<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>So the memory usage just keeps growing, despite my attempts to clean up before loading the dataset. This is from the RES (resident) column of top, and I don't think this is memory which can be reclaimed by the OS? That would show up in the VIRT (virtual) column I think.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>So my question remains: Should I do something more to get a thorough cleanup, apart from removing the vtkVolume from the renderer and deleting it (by means of a smart pointer)?<o:p></o:p></p></div><div><p class=MsoNormal>Elvis<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p>Thanks,<br>Elvis<o:p></o:p></p><div><div><p>><br>> Best,<br>><br>> Robert<br>><br>> <br>><br>> From: vtkusers [mailto:<a href="mailto:vtkusers-bounces@vtk.org" target="_blank">vtkusers-bounces@vtk.org</a>] On Behalf Of Elvis Stansvik<br>> Sent: Wednesday, August 31, 2016 5:19 PM<br>> To: VTK Users <<a href="mailto:vtkusers@vtk.org" target="_blank">vtkusers@vtk.org</a>><br>> Subject: [vtkusers] Memory not released when volumes are removed<br>><br>> <br>><br>> Hi all,<br>><br>> Before loading a new dataset into our app, I'd like to remove all existing volumes from the renderer, which I believe should lead to them being destroyed as well, since I have no other references to the volumes (currently).<br>><br>> What I tried was<br>><br>> // Remove all existing volumes<br>> auto volumes = renderer()->GetVolumes();<br>> volumes->InitTraversal();<br>> for (int i = 0; i < volumes->GetNumberOfItems(); ++i) {<br>> qDebug() << "removing volume";<br>> vtkSmartPointer<vtkVolume> volume = volumes->GetNextVolume();<br>> qDebug() << "before:" << volume->GetReferenceCount();<br>> renderer()->RemoveVolume(volume.GetPointer());<br>> qDebug() << "after:" << volume->GetReferenceCount();<br>> }<br>><br>> The output I get each time I load a new dataset (actually the same, but doing it repeatedly) and execution passes by this cleanup code is:<br>><br>> removing volume<br>> before: 3<br>> after: 1<br>> removing volume<br>> before: 3<br>> after: 1<br>> removing volume<br>> before: 3<br>> after: 1<br>><br>> Which sort of makes sense to me: Apparently the renderer holds two references to the volume, since the refcount goes down by 2 when I remove the volume from the renderer. The remaining reference is held by the vtkSmartPointer I created inside the loop.<br>><br>> But, what surprises me is that memory usage does not seem to go down when this code is executed. I would expect that when the scope of the for loop body is exited, the refcount will drop to zero, so the volume should be deleted. And I guess it probably is.<br>><br>> But looking at the memory usage when repeatedly loading datasets (and thus clearing the previous), the resident memory used by the app accumulates.<br>><br>> Must I somehow remove the mapper / underlying image data as well? I'm not holding any references to these, so I would have expected them to die along with the volume.<br>><br>> Helpful for any tips on why this cleanup is apparently not enough to avoid memory accumulation.<br>><br>> Thanks,<br>><br>> Elvis<o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>