Like suspected the ClearCanvas isn't to blame.. Turns out using the GetHbitmap() function leaves you with the responsibility of deleting the HBmp.. However, I'm not all in the clear yet though, so I'd appreciate some general feedback on whether there are any precautions to take when using the ClearCanvas library - memory vice. Is see that there are some classes with Dispose(). Am I required to call this when I'm done with the objects?

Cheers,
Stian

Hi, this is not a straightforward question to answer, but generally you should dispose any objects that you have created that don't belong to some other object. If you are simply interacting with objects contained within an ImageViewerComponent, then you can safely leave it up to the viewer to dispose it. Otherwise, any object you created in your code, you will need to dispose of it yourself.

All that being said, there are very few objects in CC that hold unmanaged resources, so although it's best practice to dispose objects that implement IDisposable, there are very few where it actually matters. The reason many of our classes implement IDisposable is because subclasses could reference an unmanaged resource that needs to be cleaned up.

Hope this helps,
Stewart

Thanks. I am disposing the LocalSopDataSource, ImageSop and IPresentationImage. Without doing so there seemed to be a memory leak, but now it's all fine.

Stian