On Sat, Nov 4, 2017 at 2:21 AM, Chet Ramey <chet.ra...@case.edu> wrote: > If it's that, it's not a leak. It's bash-4.3 keeping exit statuses for the > last CHILD_MAX processes. Bash-4.4 restricts that to the last CHILD_MAX > asynchronous background processes, with accompanying loss of functionality.
Ok, seems indeed to stall around the 50K loops (with "getconf CHILD_MAX = 63460"). So, what's the difference in handling between "< <(cmd)" and "cmd | " ? Is there any way to disable this feature ? or should we consider these 500KB low enough to live with it, regarding the current memory available on servers ?
