On 11/3/17 9:48 PM, Adrien Mahieux wrote:
> On Sat, Nov 4, 2017 at 2:21 AM, Chet Ramey 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 accompa
On Sat, Nov 4, 2017 at 2:21 AM, Chet Ramey 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
On 11/3/17 9:18 PM, Adrien Mahieux wrote:
> On Sat, Nov 4, 2017 at 1:18 AM, Chet Ramey wrote:
>> On 11/3/17 6:01 PM, Adrien Mahieux wrote:
>>> Hello,
>>>
>>> I think I've found a bug in the loop management. Maybe it's an
>>> expected behavior (didn't find any related topic on the manpages) but
>>>
On Sat, Nov 4, 2017 at 1:18 AM, Chet Ramey wrote:
> On 11/3/17 6:01 PM, Adrien Mahieux wrote:
>> Hello,
>>
>> I think I've found a bug in the loop management. Maybe it's an
>> expected behavior (didn't find any related topic on the manpages) but
>> it's annoying in long-running scripts.
>>
>> The
On 11/3/17 6:01 PM, Adrien Mahieux wrote:
> Hello,
>
> I think I've found a bug in the loop management. Maybe it's an
> expected behavior (didn't find any related topic on the manpages) but
> it's annoying in long-running scripts.
>
> The leak is triggered by this idiom (wether or not jobcontrol
