What are the reasons Process.HasExited can throw InvalidOperationException?

Question

I'm seeing a System.Diagnostics.Process.HasExited method throw an InvalidOperationException, but the message text property is not terribly useful as to why it was thrown. Under what conditions does this exception get thrown?

lmat - Reinstate Monica · Answer 1 · 2014-06-22T00:07:22.180

I'm seeing the same message. It can happen if you do this:

System.Diagnostics.Process proc = new System.Diagnostics.Process();
proc.StartInfo.FileName = "trash filename here.exe";
try
{
    proc.Start();
}
catch { }//proc should fail.
try
{
    if (proc.HasExited)
    {
        //....
    }
}
catch (System.InvalidOperationException e)
{
    //cry and weep about it here.
}

If proc.Start() failed above, you should get to cry and weep section, too. So, if you catch after proc.Start() be sure to catch at proc.HasExited (and MANY other of the System.Diagnostics.Process Methods.

score 5 · Answer 2 · answered Apr 08 '10 at 20:45

5

As Obalix correctly states, an InvalidOperationException is thrown when no process is attached to the Process object. This happens when a process has exited and Close or Dispose has been called on the Process object. Close releases all resources related to the process from memory. Before calling Close, this data was kept in memory to provide you (the programmer) with the information you want to know about the exited process, such as it's ExitTime and ExitCode.

answered Apr 08 '10 at 20:45

Daniel A.A. Pelsmaeker

47,471
20
111
157

1

+=: Until you close/dispose the object, the underlying system keeps some resources to allow you to track the old process' state. When you close/dispose it, they are released, and so the PID number (and/or handle adresses, etc) may be REUSED for another brand new process. If afterwards you tried to query them for process' state, you *could* get an (cached) information that, for example, "PID=2688 is KILLED with exitcode 0x34" while the 2688 number *could* be already running again, and you *could* screw something up. Worse: you *could* get (uncached) info on the NEW process, and surely screw up. – quetzalcoatl Jul 03 '12 at 09:06

score 3 · Answer 3 · edited May 23 '17 at 12:13

3

The documentation states that an InvalidOperation exception is thrown in no process is associated with the object.

Have you already started the process using Process.Start() or was the process disposed before you are accessing the HasExited property?

This post also deals whith the same issue.

edited May 23 '17 at 12:13

Community

1
1

answered Apr 08 '10 at 20:43

AxelEckenberger

16,628
3
48
70

score 2 · Accepted Answer · answered Apr 08 '10 at 22:16

2

If the above two answers take in mind that process's instance members aren't thread safe, so that might be the next place to start looking.

answered Apr 08 '10 at 22:16

Brandi

1,549
4
24
32

score 1 · Answer 5 · edited Nov 17 '15 at 10:33

1

Don't call Terminate.Close(), call Terminate.CloseMainWindoe() instead.

You may then issue a timed wait, check for HasExited and call Kill() if required.

edited Nov 17 '15 at 10:33

SuperBiasedMan

9,814
10
45
73

answered Nov 17 '15 at 10:11

Paul

11
1

Welcome to Stack Overflow! Please consider editing your post to add more explanation about what your code does and why it will solve the problem. An answer that mostly just contains code (even if it's working) usually wont help the OP to understand their problem. – SuperBiasedMan Nov 17 '15 at 10:33

What are the reasons Process.HasExited can throw InvalidOperationException?

5 Answers5