Re: Memory Leak Issue
- From: Stephen Kellett <snail@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 18 Aug 2006 13:37:18 +0100
In message <#p4KfzpwGHA.3964@xxxxxxxxxxxxxxxxxxxx>, Oleg Starodumov <com-dot-debuginfo-at-oleg@?.?.invalid> writes
memory leak detector would allow to take several snapshots of the application's
memory usage and show the difference - the blocks that have been allocated between
subsequent snapshots. Currently UMDH tool (available as part of Debugging Tools
for Windows) can do it. The same can be done using WinDbg.
With Memory Validator you can insert watermarks at any point and then display data between arbitrary watermarks. Not the same as what you describe, but can be used to identify behaviour between different points of the application.
Stephen
--
Stephen Kellett
Object Media Limited http://www.objmedia.demon.co.uk/software.html
Computer Consultancy, Software Development
Windows C++, Java, Assembler, Performance Analysis, Troubleshooting
.
- Follow-Ups:
- Re: Memory Leak Issue
- From: Oleg Starodumov
- Re: Memory Leak Issue
- References:
- Memory Leak Issue
- From: MiTz
- Re: Memory Leak Issue
- From: Oleg Starodumov
- Re: Memory Leak Issue
- From: MiTz
- Re: Memory Leak Issue
- From: Oleg Starodumov
- Memory Leak Issue
- Prev by Date: Re: Memory Leak Issue
- Next by Date: Sample Program for Code Analysis Tool
- Previous by thread: Re: Memory Leak Issue
- Next by thread: Re: Memory Leak Issue
- Index(es):