I think the hardest part for me with the code is tracking down all the memory leaks. These occur when you grab a section of your computer's memory, but forget to tell the computer that you're finished with it.
Our first line of defense is a nifty program called Visual Leak Detector (VLD) which tells you exactly what wasn't released. The only problem is that it doesn't detect heap corruptions, which is currently what our code contains. Even worse is that they only show up on a release build.
The only way to track them down (that I know anyway) is to look through the code line by line until the problem has been found. I must have looked through it a million times by now but there still seems to be problems.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment