[Insight-developers] memory leaks and ProcessObject::UnRegister()

[Bill Hoffman]

This is a known bug that we are working on.
Due to the reference count loops created in the pipeline,
the process object leaks right now.   Porting the VTK solution
to ITK will be some what involved, because VTK does not use smart
pointers, and passes values to UnRegister to detect loops.

-Bill


At 12:03 PM 11/28/00 -0800, Lydia Ng wrote:
>Hi,
>
>I was trying to build a application
>using itk and noticed I was getting memory
>leakage. 
>
>I tracked it down to ProcessObject::UnRegister()
>which currently does nothing.
>
>In my application, I create a new filter via New()
>and get a smartpointer to it. When my smartpointer
>goes out of scope, I presume it should also delete
>my filter since there is no other references to it.
>
>Because ProcessObject::UnRegister() does nothing
>the destructor for the filter is never called 
>and hence the memory leak.
>
>Should ProcessObject::UnRegister() do something
>similar to DataObject::UnRegister() which eventually
>activates a delete, or should I be cleaning up
>my filter some other way?
>
>Lydia
>
>
>_______________________________________________
>Insight-developers mailing list
>Insight-developers at public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers