How to see if there are any memory leaks (Visual Studio 6, DirectX)

Started by
4 comments, last by Subotron 21 years, 2 months ago
Well, the title says it all. Setting thing up, ok. But what do I have to de-initialize? And how? How do I find out if I don''t have any memory leaks or other wrong/not de-initialized things? If it helps, I use Visual Studio 6 enterprise edition and the DirectX API. Any other hints on this topic are welcome too Thanks in advance!
Advertisement
I''ve read someone has written a layer on
alloc stuffs (new/delete, malloc/free) which
is totally transparent that is exactly do
what you''re looking for.
But i can''t remember his name ... Try in
the code of the day database here @ GD or
maybe an article.
Hope it helps

article from flipcode about memory leaks - I think this might be what cnstrnd was talking about
I've found that the one on flipcode doesn't catch all the leaks.

Use the fluid studios manager instead:

http://www.fluidstudios.com/publications.html



[edited by - jamessharpe on January 20, 2003 12:09:02 PM]
msvc already comes with a debug heap.
James: You found it ! thousands thanks !

--

Following niyaw guidance if found that :

Detecting and Isolating Memory Leaks Using Microsoft Visual C++


[edited by - cnstrnd on January 21, 2003 8:25:12 AM]

This topic is closed to new replies.

Advertisement