Evening all,
One of those classic moments where I've completely confused myself [sad] I know I've done this before (
somehow) but I've forgotten.
In testing out some memory leak checking stuff, I modified one of the DXSDK samples so it didn't release one of the ID3DXMesh objects. Consequently you get:
Direct3D9: (INFO) :MemFini!
Direct3D9: (ERROR) :Memory still allocated! Alloc count = 149
Direct3D9: (ERROR) :Current Process (pid) = 00000e28
Direct3D9: (ERROR) :Memory Address: 00da4f94 lAllocID=1 dwSize=000047f8, ReturnAddr=00fc14db (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00dab944 lAllocID=9 dwSize=00001290, ReturnAddr=00fb8044 (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00dab84c lAllocID=10 dwSize=00000008, ReturnAddr=00fb8132 (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00dacc0c lAllocID=11 dwSize=000003a0, ReturnAddr=00fb970f (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00dab88c lAllocID=12 dwSize=00000044, ReturnAddr=00fc14db (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00da97c4 lAllocID=13 dwSize=00000050, ReturnAddr=00fc14db (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00da9ae4 lAllocID=22 dwSize=000006bc, ReturnAddr=00fd2f4b (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00dacfe4 lAllocID=24 dwSize=000016c8, ReturnAddr=00fc4a19 (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00dab904 lAllocID=26 dwSize=00000008, ReturnAddr=00fc4b5d (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 01290064 lAllocID=28 dwSize=00003508, ReturnAddr=00fc14db (pid=00000e28)
Direct3D9: (ERROR) :Memory Address: 00daa1d4 lAllocID=29 dwSize=00000198, ReturnAddr=00fc14db (pid=00000e28)
Direct3D9: (ERROR) :Total Memory Unfreed From Current Process = 45808 bytes
Now, I was pretty sure I remembered that the lAllocID field for each (ERROR) could be used to find the offending object. There are lots more (ERROR) entries than actual leaks because it's reporting the owners of the leaked object as well.
So, I fire up the control panel:
And plug in my 11 values for the
"Break On AllocID" field. Run my application again, and they all point to either the Direct3DCreate() or CreateDevice() call. None of them go to the ID3DXMesh that is actually being leaked.
Through a bit of random checking, the ID3DXMesh mesh is actually lAllocID=146; which breaks where expected (on a D3DXLoadMeshFromX() call).
Now, what I was wondering - anyone here tell me which bit it is that I'm forgetting/missing? I'm ready and waiting to be pointed and laughed at for being stupid [smile]
Cheers,
Jack
