this isn't a mega-points question because I'm only interested in opinions here.
We have a large application that has been created with mostly managed code, although it also runs unmanaged code, some of which we have written, other parts are libraries (eg device drivers).
The application works with heavy Bitmap object traffic - creating, and destroying where it seems appropiate. However, we are getting some pretty big memory leaks. Some of the areas of leaks can be found using common sense, others are harder to find.
I'd like to know about tools that we could use to help us with the problem. I am aware that for unmanaged code there are some pretty powerfull profilers out there that can even tell you exactly where the application is leaking - compiling the project with the profiler libs etc...
For .NET however, these kind of highly developed tools are hard to find. I have seen one called
.NET Memory Profiler (http://www.scitech.se/
Any comments on the practise of handling Bitmap objects in .NET?