<p>I use Visual Studio 2012 and VLD 2.2.3.</p>
<p>Compile option /MTd.</p>
<p>Memory leak is reported with the next code.</p>
<p> </p>
<p>int _tmain(int argc, _TCHAR* argv[])</p>
<p>{</p>
<p> return 0;</p>
<p>}</p>
<p> </p>
<p>VisualLeakDetector::_HeapCreate() dose not seem to be called...</p>
<p> </p>
<p>*I use machine translation, I cannot express it well.</p>
Comments: Same here--- Is this a VisualLeakDetector problem or is this the CRT??? I can believe the CRT leaks, but WHY doesn't VLD have a way to "screen out" these reports? if they're known, then just give us an .INI entry to automatically ignore faults of this type... OR is it that VLD exits before the CRT cleans up?
<p>Compile option /MTd.</p>
<p>Memory leak is reported with the next code.</p>
<p> </p>
<p>int _tmain(int argc, _TCHAR* argv[])</p>
<p>{</p>
<p> return 0;</p>
<p>}</p>
<p> </p>
<p>VisualLeakDetector::_HeapCreate() dose not seem to be called...</p>
<p> </p>
<p>*I use machine translation, I cannot express it well.</p>
Comments: Same here--- Is this a VisualLeakDetector problem or is this the CRT??? I can believe the CRT leaks, but WHY doesn't VLD have a way to "screen out" these reports? if they're known, then just give us an .INI entry to automatically ignore faults of this type... OR is it that VLD exits before the CRT cleans up?