3

I have a Process that I want to Kill; however sometimes this produces the InvalidOperationException that says that the process has already exited.

To prevent the exception, I tried to check whether the process exited:

if (!p.HasExited)
{
    p.Kill();
}

However, I still occasionally see the exception. Since the process is running in parallel with my code, I assume that the problem could be essentially a race condition, i.e. the process terminating inbetween the check and the Kill() call.

What is the proper way to kill a process without raising the said exception? Of course that I can try-catch around the code in question, but that just doesn't seem like the best way to solve this.

mzi
  • 307
  • 3
  • 10

2 Answers2

8

You wouldn't be able to fix this problem, because there is a built-in race condition: the process may be alive at the time when you call p.HasExited, but by the time when your program calls p.Kill() it could already have exited.

A separate process is inherently a concurrent entity, so you would need some form of synchronization in order to solve this race condition. However, this problem cannot be solved in situations when you do not own the code of the process in question, because there is no way to synchronize activities of your program that monitors the process in question and the process itself.

You should send the kill signal unconditionally, trap the specific exception, and move on.

Sergey Kalinichenko
  • 714,442
  • 84
  • 1,110
  • 1,523
3

The proper way is to attempt to exit the process and catch the exception. The process could have ended in the time between you checking and invoking the exit.

Grice
  • 1,345
  • 11
  • 24