Process.WaitForExit Question

[stoogots2]

I have written a windows application that kicks off another process and then Waitsforexit. I have one old crappy machine on which this works great and has been for months and in the last couple of months I've seen that on a newer faster machine that it doesn't seem to work reliably. Both are XP SP3 and the app utilizes Framework 2.0. Any ideas?

ProcessStartInto ps=new ProcessStartInfo();
ps.FileName=sFilename;
ps.Arguments=sArguments;
ps.WorkingDirectory=sWorkingDirectory;
p.EnableRaisingEvents=true;

p=Process.Start(ps);
try
{
p.WaitForExit();
TaskStopped(p);
p.Close();
}
catch (Exception ex)
{
//Log Error Message only
}

[Plater]

What do you mean doesn't work reliably?
Is the process starting and ending faster then you can follow on the newer machine perhaps?

[stoogots2]

Thanks for the response Plater. The process usually takes about 90 minutes to complete but another thread checks every minute to make sure it takes no longer than 180 minutes or it kills it. I saw in the log that the process got killed after 180 minutes although the output that was expected from the process was completed in the normal timeframe. I've seen this more than once, but only on this one computer. I have 3 other computers running the same code without ever having experienced this problem.

[Plater]

So its not the waitforexit() that's failing, its that the process is never exiting.

[stoogots2]

I have every indication that the process is exiting except that I do not see the WaitForExit completing and the paused thread continuing. The output of the process is there and in all other cases where this code is executing, the process has exited. There shouldn't be anything different about the 5th machine running the same application/framework/operating system/service pack.

[Plater]

I thought you said you had a seperate thread that is checking to make sure the processes ended and kills it if it didn't. If you can still see the process in that thread, it had never ended

[stoogots2]

The main thread just waits a configurable amount of time and Process.Kills the worker thread if it doesn't proceed past p.WaitForExit() .

[Plater]

Hmm is there any reason it NEEDS to wait for exit? If it just gets killed off anyway?

[stoogots2]

Yes, there is a need for it to waitforexit. It only gets killed off if there is not a problem, so in most cases it won't get killed. I kill the process only when it has run for twice the "normal" completion period without completing. The problem is that if there isn't a problem, it doesn't seem to return from WaitForExit every time. I have 3 other instances of the same program running and returning from WaitForExit every time. It is just strange that the new computers don't return each and every time.

[GaryTexmo]

Out of curiosity, have you tried using the event handler on the process object? I'm not saying you should use it instead, I'm just curious of the callback works for you, whereas the waitforexit seems to be behaving oddly.

                Process myProcess = new Process();
                myProcess.StartInfo.FileName = ...;
                myProcess.StartInfo.Arguments = ...;
                myProcess.EnableRaisingEvents = true;
                myProcess.Exited += new EventHandler(mergeToolProcess_Exited);

                myProcess.Start();