I opened AppVerifier and open the basic leak options. Then I run my app named setup.exe. I got a exception when calls SetupDiCallClassInstaller to uninstall a avstream audio miniport driver.
Based on the given information, I found not setup.exe but a dll named MMDevAPI.dll has leaked memory. It’s a system supplied DLL( based on the name, I thinks it’s associated with multimedia, and so avstream audio driver).
My bug or MMDevAPI?
Appreciated.
=======================================
VERIFIER STOP 00000900: pid 0x174C: A heap allocation was leaked.
0E87CFE8 : Address of the leaked allocation. Run !heap -p -a
00D1CCF4 : Address to the allocation stack trace. Run dps to view the allocation stack.
0E854FE0 : Address of the owner dll name. Run du to read the dll name.
74310000 : Base of the owner dll. Run .reload = to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.
=======================================
This verifier stop is continuable.
After debugging it use `go' to continue.
=======================================
0:001> du 0E854FE0
0e854fe0 "MMDevAPI.DLL"
0:001> !heap -p -a 0E87CFE8
address 0e87cfe8 found in
_DPH_HEAP_ROOT @ 171000
in busy allocation ( DPH_HEAP_BLOCK: UserAddr UserSize - VirtAddr VirtSize)
e861e38: e87cfe8 18 - e87c000 2000
6b258e89 verifier!AVrfDebugPageHeapAllocate+0x00000229
76f84f7e ntdll!RtlDebugAllocateHeap+0x00000030
76f47e1e ntdll!RtlpAllocateHeap+0x000000c4
76f1353a ntdll!RtlAllocateHeap+0x0000023a
6b4dfd2c vfbasics!AVrfpRtlAllocateHeap+0x000000b1
// Why go into MMDevAPI? It's only available in Win7.
74311438 MMDevAPI!operator new+0x00000017
7431f038 MMDevAPI!CreateDeviceTopologyCache+0x0000001d
7431e38a MMDevAPI!DllMain+0x0000004d
7431e274 MMDevAPI!_CRT_INIT+0x0000026d
6b26c66d verifier!AVrfpStandardDllEntryPointRoutine+0x00000099
6b5b898c vrfcore!VfCoreStandardDllEntryPointRoutine+0x00000128
6b4df544 vfbasics!AVrfpStandardDllEntryPointRoutine+0x00000097
76f1afc4 ntdll!LdrpCallInitRoutine+0x00000014
76f1fdce ntdll!LdrpRunInitializeRoutines+0x0000026f
76f2027b ntdll!LdrpLoadDll+0x000004d1
76f1f699 ntdll!LdrLoadDll+0x00000092
6b4df2c7 vfbasics!AVrfpLdrLoadDll+0x00000049
7520b8a4 KERNELBASE!LoadLibraryExW+0x0000015a
756a28e3 kernel32!LoadLibraryW+0x00000011
74177b3b WINMM!LoadAliasedLibrary+0x0000014f
74177751 WINMM!InternalLoadDriver+0x0000014b
74177c0d WINMM!InternalOpenDriver+0x00000034
74177bbd WINMM!DrvOpen+0x00000054
6b2c4f51 mmci!RemoveDriver+0x000001e4
6b2c555c mmci!Media_RemoveDevice+0x00000014
6b2c3fdb mmci!MediaClassInstaller+0x00000045
76d34a1b SETUPAPI!_SetupDiCallClassInstaller+0x00000b91
76d344f8 SETUPAPI!SetupDiCallClassInstaller+0x0000004e
// below call stack belong to my own app.
0054a408 Setup!RemoveDriverForSpecifiedDevice+0x00000088
0054beb2 Setup!RemoveDriver+0x000002e2
0054c138 Setup!RemoveMiBoxDriver+0x00000068
005552b2 Setup!ProgressComponent::run+0x00000182