dotnet/runtime
GitHub で見るProcess.StandardOutput.Peek() and Process.StandardError.Peek() hang until StreamReader receives data.
Open
#91,891 opened on 2023年9月11日
area-System.Diagnostics.Processhelp wanted
Repository metrics
- Stars
- (17,886 stars)
- PR merge metrics
- (平均マージ 12d 11h) (30d で 661 merged PRs)
説明
Closing this issue because I cannot reproduce it reliably.
Originally posted by @jscarle in https://github.com/dotnet/runtime/issues/74677#issuecomment-1228951480
The original issue suggested to repro the problem using the Process.StandardOutput which is suboptimal because most of the processes we usually run produce some output. The issue shows itself only when output is empty. Just try the same but with the Process.StandardError. In most of the cases there will be no data in that stream and the issue will reproduce.
var process = Process.Start(new ProcessStartInfo("path\to\executable.exe", arguments)
{
CreateNoWindow = true,
UseShellExecute = false,
RedirectStandardInput = true,
RedirectStandardOutput = true,
RedirectStandardError = true,
StandardOutputEncoding = Encoding.UTF8,
StandardErrorEncoding = Encoding.UTF8
});
var outputBuilder = new StringBuilder();
while (process.StandardError.Peek() > -1)
outputBuilder.Append((char)process.StandardError.Read());
var result = outputBuilder.ToString();