Hi there, this may or may not help your locking problem.
We had a case a while ago where we convert several MITK images into several ITK images, and then run them through multiple filters pipelined together, and copied the resultant ITK image back to MITK. The ITK pipeline itself was persisted between calls for performance reasons to reduce the setup/tear-down time, and to avoid repeatedly re-allocating memory buffers within each ITK filter. I found that for ALL my ITK filters I had to explicitly set all filter input connections to NULL after using the filters, and this was what enabled the smart pointers to release. I have no idea why this actually helped, but I do remember wasting a lot of time on it :-) Hope that helps. M ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
