Re: Weird crash in d3dx9_30.dll

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Richard [Microsoft Direct3D MVP] <legalize+jeeves@xxxxxxxxxxxxxxxxx>
loquated like no one had ever loquated before with:

[Please do not mail me a copy of your followup]

"WTH" <wth@xxxxxxxxxx> spake the secret code
<O7UKyWHoGHA.4124@xxxxxxxxxxxxxxxxxxxx> thusly:

It seems as though D3DX is reacting to some windows message
generated by the CFileDialog when it is supposed to display a
tooltip over a file object.

Sorry, that ain't happenin. D3DX isn't wired to your window *at all*.

D3D is wired to your focus window, but it doesn't call into D3DX.

This just sounds like your own application has corrupted memory
somewhere, somehow, and its resulting in this side effect.

Try running bounds checker or purify on your application to spot
abuses of memory/pointers.

Using the heap debugger from MS results in the same indications. No
stack/frame corruption, and D3DX is pointed to as a culprit.

I'll bounds check it when I get a chance...

WTH



--
"I'm not giving away any secrets like that to Milan. If I had my way,
I wouldn't even tell them the time of the kick-off." - Bill Shankly


.