Resource Leaks: Detecting, Locating, and Repairing Your Leaky GDI Code

Posted: Feb/13/2001 By: pankaj Points:15 Category: .NET - .NET Framework Views:75 Vote Up (0) Vote Down (0)

Leaks are possible, even in robust Windows-based applications. As bugs go, leaks are some of the most difficult to find, especially when they occur in graphics device interface (GDI) objects and menus. While free and third-party tools exist to detect such leaks, it is usually difficult to make the connection between the numeric handle value returned by the tool, and a bitmap or menu in your program. This can limit the usefulness of these tools. Custom tools can be built that detect, track down, and eradicate GDI and menu leaks. Here, three such tools are built using well-known and documented APIs.Christophe NasarreMSDN Magazine March 2001

View Complete Post

Comments:

Be the first to comment this post.

Post Comment

Please login to post your comment

More Related Resources

How to Detect and Avoid Memory and Resource Leaks in .NET Applications.

I'll explain in this article why memory leaks exist in .NET and how to avoid them. Don't worry, I won't focus here on the inner workings of the garbage collector and other advanced characteristics of memory and resources management in .NET.

It's important to understand leaks and how to avoid them, especially since they are not the kind of things that is easy to detect automatically. Unit tests won't help here. And when your application crashes in production, you'll be in a rush looking for solutions. So, relax and take the time to learn more about this subject before it's too late.

Code Cleanup: 9 Useful Tactics for Paying Back Technical Debt

Now that you've identified technical debt in your code base, let's turn our attention to some specific tactics that will help you pay back that debt.David LaribeeMSDN Magazine January 2010

Generation Test: Automated Unit Tests for Legacy Code with Pex

Creating and maintaining a unit test suite for legacy code can be a challenge. Pex automatically produces a small test suite with high code and assertion coverage.Nikhil SachdevaMSDN Magazine December 2009

Code Cleanup: Using Agile Techniques to Pay Back Technical Debt

Every codebase contains some measure of technical debt - code that is maddeningly hard to test and maintain. We outline some ideas for identifying and dealing with the high-interest debt in your code.David LaribeeMSDN Magazine December 2009

Synchronization Coverage: Code Coverage for Concurrency

As more and more multi-threaded software applications get developed, software development professionals need to adopt new tools, techniques and metrics that can deal with multi-threaded software. Synchronization coverage is a simple, practical way to do this and this article covers a prototype synchronization coverage tool for .NET, called Sync Cover.Chris Dern, Roy TanMSDN Magazine September 2009

Toolbox: Data Snapshots, Subversion, Source Code Organization and More

If you want to save, organize, and annotate snapshots of your database data, find an easy way to install and configure Subversion, and automate the organization of your source code, then you'll want to read more about these latest tools.Scott MitchellMSDN Magazine August 2009

Resource Leaks: Detecting, Locating, and Repairing Your Leaky GDI Code

How to Detect and Avoid Memory and Resource Leaks in .NET Applications.

Code Cleanup: 9 Useful Tactics for Paying Back Technical Debt

Generation Test: Automated Unit Tests for Legacy Code with Pex

Code Cleanup: Using Agile Techniques to Pay Back Technical Debt

Synchronization Coverage: Code Coverage for Concurrency

Toolbox: Data Snapshots, Subversion, Source Code Organization and More

CLR Inside Out: Code Contracts

Under the Table: How Data Access Code Affects Database Performance

Inside Microsoft patterns & practices: Building WPF and Silverlight Applications with a Single Code

Wicked Code: Taking Silverlight Deep Zoom To The Next Level