0

Question is simple, as in title: Why D3DXCreateTexture() sometimes fails with E_OUTOFMEMORY when running with Application Verifier? Without it - everything works fine. Well, almost, of course there's a reason I'm using App Verifier: I'm suspecting that there's a few heap corruption situations inside my code, but this error never happened running either in debug or release - only with App Verifier (then it happens in debug and in release). Dr. memory isn't too specific when it comes to it's results, and mainly points to 3rd party libraries (openssl, freefont, directx, etc), not to code I'm talking about. Do any of You have some idea, what is happening? Thanks in advance.

baderman
  • 126
  • 3
  • 10

1 Answers1

0

Fortunately, I've found answer here on StackOverflow. Here is issue, and answers: one in comment by @Chad and second as qualified answer by @James McNellis. Thanks Guys!

Community
  • 1
  • 1
baderman
  • 126
  • 3
  • 10