Direct3D9: (ERROR) : [7] : Address 004B50B4
Direct3D9: (ERROR) : [8] : Address 7C816D4F
Direct3D9: (ERROR) : [9] : Address 00000000
Direct3D debug
Author
How do I know why Direct3D lists approx. 2000 errors when application quits.
They're all like this:
Is that quite literally a quote from the debug output, or is it a bit more like what I wrote in the NeXe entry on debugging?
What you've quoted looks/sounds a bit like the memory leak messages, but I've not seen them outputted the same as you're posting [smile]
hth
Jack
Quote:Direct3D9: (INFO) :MemFini!
Direct3D9: (ERROR) :Memory still allocated! Alloc count = 132
Direct3D9: (ERROR) :Current Process (pid) = 0000055c
Direct3D9: (ERROR) :Memory Address: 00da4f94 lAllocID=1 dwSize=000047f8, ReturnAddr=00fc14db (pid=0000055c)
Direct3D9: (ERROR) :Total Memory Unfreed From Current Process = 49836 bytes
What you've quoted looks/sounds a bit like the memory leak messages, but I've not seen them outputted the same as you're posting [smile]
hth
Jack
That sounds like a memory leak. Go into the SDK control panel and select Break on Memory Leak and trying running your program in Debug mode again.
Debuggin D3D Memory Leaks
Update: Jack is too quick for me.
Debuggin D3D Memory Leaks
Update: Jack is too quick for me.
Quote:Original post by skittleo
Update: Jack is too quick for me.
[lol] I live in these forums
Anyway, for the OP, check out the links and if you've got time take a look around NeXe - it's a great resource [grin]
Jack
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
