WaitForExit sometimes (randomly) doesn't work

Question

The code (only part) works properly most of the time, but it sometimes just hang there and the lines after try...catch block seem not to be called even if the process in the task manager doesn't exist any more.

Because most of the time there's just no problem with it, I can't reproduce the issue while debugging. Can any one give me a hint why or on what condition will this happen?

try {
    process.Start();
    process.BeginOutputReadLine();
    process.BeginErrorReadLine();
    process.WaitForExit(settings.PlinkConnectTimeout * 1000);
    if (process != null && !process.HasExited) {
        if (IsConnected) {
            process.WaitForExit();
        }
        else {
            process.Kill();
        }
    }
}
catch { }

IsConnected = false;
IsConnecting = false;
Disconnected(isLastSuccess, isReconnect);

How do you know that the lines after try-catch block are not called? — Andrew Savinykh, Feb 08 '13 at 06:25
I can't promise that. But if they are called, some UI changes should have been triggered. — vilicvane, Feb 08 '13 at 06:30
possible duplicate of [ProcessStartInfo hanging on "WaitForExit"? Why?](http://stackoverflow.com/questions/139593/processstartinfo-hanging-on-waitforexit-why) — Andrew Savinykh, Feb 08 '13 at 06:31
possible duplicate of http://stackoverflow.com/questions/439617/hanging-process-when-run-with-net-process-start-whats-wrong — Andrew Savinykh, Feb 08 '13 at 06:31
Seems not to be the same issue, as I am using BeginOutputReadLine and BeginErrorReadLine. — vilicvane, Feb 08 '13 at 06:38

WaitForExit sometimes (randomly) doesn't work

0 Answers0