memory bound for process::Child::wait_with_output

Hi Folks: I just ran into an issue where I

let test = Command::new("yes").stdout(Stdio::piped()).spawn().unwrap();
let _res = test.wait_with_output();

and that immediately allocated 16 gigs of memory and OOM'd my machine.

Would it be possible to add a (required or optional) memory bound to wait_with_output or a new function like that?

This will also allow easy interoperability with SECCOMP jailed subprocesses.

The proposal could look something like this

Wait With Bounded Output

fn wait_with_bounded_output(self, max_stdout_bytes : usize, max_stderr_bytes : usize) -> Result

Simultaneously waits for the child to exit and collect all remaining output on the stdout/stderr handles, returning an Output instance until the max_stderr or max_stdout bounds have been reached.

If either bound has been reached, the function returns success = false, code = None in the ExitStatus and one of the two Vec will be filled to either max_stdout_bytes or max_stderr_bytes respectively
This function may be invoked again until both vectors have excess capacity.

Does this sound acceptable to the community? If so, I can draft an RFC pull request.

Start by reviewing process::Child::wait_with_output and the proposed bounded-output behavior described in the issue. Determine the API and RFC changes needed for bounded stdout and stderr collection, including repeated invocation and exit-status behavior. Done means an accepted design or RFC pull request that addresses the stated memory and output-bound requirements.