大型标准输入的C＃流程中断

Question

I need to Encrypt the content of file by GnuPG encryption. for that, I am fetching content from FILE and passing it Process via StandardInput. For small data it is working fine but when I try to Write StandardInput of more than 500KB data, program gets stuck.

    process = new Process();
     process.StartInfo.WorkingDirectory = _bindirectory;
     process.StartInfo.RedirectStandardInput = true;
     process.StartInfo.RedirectStandardOutput = true;
     process.StartInfo.RedirectStandardError = true;
     process.StartInfo.FileName = gpgExecutable;
     process.StartInfo.Arguments = gpgOptions;
     process.StartInfo.UseShellExecute = false;
     process.StartInfo.CreateNoWindow = true;

     process.Start();
/*****Here is the line where Compiler Process Stucks on large data****/
     process.StandardInput.Write(inputText); 
     process.StandardInput.Flush();
     process.StandardInput.Close();

     process.OutputDataReceived += process_OutputDataReceived;
     process.ErrorDataReceived += process_ErrorDataReceived;
     process.BeginErrorReadLine();
     process.BeginOutputReadLine();
     process.WaitForExit();

Please suggest a solution? Should i send data of file in chunks???

Answer 1

By the way, what is the data that you are trying to pass through? is it text or binary data? If binary, try writing to the StandardInput.BaseStream instead. I think that stdin is in textual mode by default and can get broken if passed some certain bytes like EOF or NULL.. see https://stackoverflow.com/a/1284753/717732

Edit:

I as right in my comment - if the child process does not read the data fast enough (or doesn't read at all) the stream buffer will get choked and all writes will block, just like reads block when the buffer is empty. See for example How to avoid standard input getting stuck in c# process

You may verify this easily: create a tiny application which reads from stdin in an infinite loop. Then, temporarily replace your gpgexecutable path with a that one tiny test app and see if blocks or not. It most probably will not block.

You should definitely check why the child process is not reading the data you try to send. Maybe commandline parameters are wrong? Or if everything seems fine and it is just the childprocess working so slowly (you can check the process' activity in TaskMonitor - does the gpg sleep or spin?), then put the stream-writing code into some backgroundworker..