Sign in to follow this  

Direct3D debug

This topic is 4530 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

How do I know why Direct3D lists approx. 2000 errors when application quits. They're all like this:
Direct3D9: (ERROR) :    [7] : Address 004B50B4
Direct3D9: (ERROR) :    [8] : Address 7C816D4F
Direct3D9: (ERROR) :    [9] : Address 00000000
I mean like: numbers may vary.

Share this post


Link to post
Share on other sites
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?

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

Share this post


Link to post
Share on other sites

This topic is 4530 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this