Why do some double delete callstacks show no allocation location?
Some double delete callstacks do not show the allocation location. There are four possible causes for this. Memory Validator was not collecting data when the memory was allocated. This could be because the memory was allocated before Memory Validator was attached to the process, or because data collection was turned off when the memory was allocated. Memory Validator has discarded the information about the memory allocation. This can happen if the Discard stack traces for freed memory check box is selected on the Misc tab of the Data Collection Settings dialog box. A possible cause is that the memory was allocated and then deleted in a statically linked CRT used by one DLL in the program, and then a pointer to the memory was also deleted by operator delete in the MSVCRT.DLL or MSVCRTD.DLL. Memory Validator does not track allocations made in the statically linked CRT, Memory Validator only tracks allocations made using the dynamically linked CRT (MSVCRT.DLL/MSVCRTD.DLL). A possible caus
