Memory Validator - Leak and Error Detection

Memory Validator detects many types of memory leak and memory error.

• Memory leaks.
  
  Detect memory allocated with the following functions, but which is not deallocated.
  • new
  • malloc
  • calloc
  • realloc
  • _expand
  • LocalAlloc
  • LocalRealloc
  • GlobalAlloc
  • GlobalRealloc
  • HeapAlloc
  • HeapReAlloc
  • VirtualAlloc
  • VirtualAllocEx
  • IMalloc
  • CoTaskMemAlloc
  • CoTaskMemReAlloc
  • user defined heaps (requires linking with memValidatorStub.lib to access this functionality)
  • user defined reference counted objects (requires linking with memValidatorStub.lib to access this functionality)
    
    
• Resource leaks - Detect resource leaks. Typical leaks are handles that are not closed
• Incorrect leak freeing - Typically this is caused by freeing a pointer that was not allocated from the appropriate heap
• Multiple leak freeing - Typically this is caused by freeing the same pointer more than once
• Heap overruns - This is the detection of writing past the end of an allocated heap block
• Heap underruns - This is the detection of writing past the start of an allocated block
• Heap corruption - Detection of the heap getting damaged by heap overruns, heap underruns and wild pointer writes
• Stack overruns - This is the detection of writing past the end of the current stack frame
• Stack underruns - This is the detection of writing past the start of the current stack frame
• Uninitialised data in C++ objects - Detection of C++ objects that do not initialise all their member variables
• COM leaks
• Reference counting for user managed heaps
• Memory leaks from user managed heaps
• Potentially unused memory
• Potentially leaked memory

This picture shows some leaked memory (yellow), some memory that was still in use at the end of the program (teal) and some memory which has not been initialised (purple). 



Click the picture for a larger image.

   Go to Top ^^