Here is a problem I'm having: sometimes, the apps that TheIDE launches for debugging remain hung up.

This is an ancient issue, at least 3 years old, but in the past it happened incredibly rarely, like single digit times/a year.

Now it happens between 2-3 times a week up to 5-6 times a day.

The executable becomes impossible to write to and I can't close it at all, even with End process tree from task manager. I used to have to restart Windows to fix it.

But now I found a solution. Close TheIDE, delete the file and restart TheIDE. The delete might be optional.

So TheIDE must be keeping my application "closed" but still loaded in memory.

Anybody else having this problem?

Maybe we should add a check to TheIDE: if it thinks that the application is closed, maybe it should go over the process tree and if the application is found, give a message? At least for debugging this hang up?

I looked over Pdb.Stop() and don't see why it would fail. It call CloseHandle on both process and thread handles.

The only idea I have is to check every single WinAPI call and MessageBox on a fail .

Sure. This issue is ridiculously annoying. Especially since I need more version of TheIDE running at once and once I have to close one because of this issue, I have to close them all because the re-opened one is in a different order on the task-bar and I have strong muscle memory and end up clicking on the wrong one.

So far TerminateProcess fails and also my PromptOK causes TheIDE to crash .

TerminateProcess is asynchronous; it initiates termination and returns immediately. If you need to be sure the process has terminated, call the WaitForSingleObject function with a handle to the process.

Alternatively, this could be meaningful:

Quote:

TerminateProcess is asynchronous; it initiates termination and returns immediately. If you need to be sure the process has terminated, call the WaitForSingleObject function with a handle to the process.

https://msdn.microsoft.com/en-us/library/windows/desktop/ms6 86714(v=vs.85).aspx

mirek wrote on Fri, 16 February 2018 13:26

Alternatively, this could be meaningful:

Quote:

TerminateProcess is asynchronous; it initiates termination and returns immediately. If you need to be sure the process has terminated, call the WaitForSingleObject function with a handle to the process.

https://msdn.microsoft.com/en-us/library/windows/desktop/ms6 86714(v=vs.85).aspx

That might be it. Since I added the logs, there were some failures, but not on TerminateProcess and no hang ups. Maybe the time it took to write the logs is enough for TerminateProcess to finish and no lock ups?

Well, you know how this goes. I program in phases on different projects, and only 3 are in U++. So there are a couple of months of U++ work and activity on forum and then I'm gone .

I'm back now for a couple of months and another feature phase on my projects, so back to the old problems.

I got today one of these signature debugger hangs.

I'm testing:

WaitForSingleObject(hProcess, INFINITE);

I'll get back to you in a few days to see if this helps in any way...

Continuation: https://www.ultimatepp.org/forums/index.php?t=msg&goto=5 0621&#msg_50621