[10.50b1 x64] Unhandled exception when closing separate search by AHK script

[AntonyD]

2Hacker
Ok, let's try to walk through the steps from Author:
https://www.ghisler.ch/board/viewtopic.php?p=413369#p413369

[Hacker]

AntonDudarenko,
Good idea, thank you, but no .dmp file has been created, unfortunately.

Roman

[AntonyD]

ok, try this:
procdump.exe -accepteula -ma -e -x <path-to-folder-where-DMP-will-save> <path-to-totalcmd64.exe>
like:
procdump.exe -accepteula -ma -e -x C:\Dumps C:\TotalCmd\TOTALCMD64.exe

[Hacker]

AntonDudarenko,
Thank you, but still nothing. Wouldn't the parent TC need to crash for a dump to be created or so?

Roman

[ghisler(Author)]

You don't need to provide a crash dump, I can reproduce it with your AHK script.

By the way, this behavior only happens in the 64-bit version and only since v10.50b1.

Not true, I can a crash dump with TC10. It doesn't happen with 9.51, though.
So far I could not find the reason, I get the same WM_SYSCOMMAND, SC_CLOSE as when I click on the X button...

[Hacker]

Christian,

You don't need to provide a crash dump, I can reproduce it with your AHK script.

Ah, great, thank you.

Not true, I can a crash dump with TC10.

Hmm, strange, I wasn't able to reproduce it. Sorry for the wrong information then.

I get the same WM_SYSCOMMAND, SC_CLOSE as when I click on the X button

Couldn't the problem be that you get it twice (once from the actual click, a second time from the script)?

Roman

[ghisler(Author)]

No, I checked it in the debugger, I only get it once.

[white]

No, I checked it in the debugger, I only get it once.

Because the crash happens when it tries to do so? Window is already closed when it tries to send the message?

[ghisler(Author)]

That's a possibility. I now solved it by setting a short 0.1 second timer when I receive WM_CLOSE, and only close the window when that timer ends. This way all pending messages can still be handled before I close the window.