Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop

2020-04-02 Thread Vitaly Zuevsky
Hi Harald, Thanks for comprehensive account of the job flow - all worked as expected now. Interestingly, I originally assumed it was a bug due to observed discrepancy with bash... On 29/03/2020 23:07, Jilles Tjoelker wrote: > I agree that the change is incorrect, but I do not agree that this

Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop

2020-03-31 Thread Vitaly Zuevsky
Hi Harald, > set -- $(seq 1 100) > for i > do > : & > sleep .1 > done > for i > do > wait %$i > done > >This is a valid script and works fine in dash. Your change breaks this by not >keeping the jobs around long enough, and I hope this test script shows that >there is

Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop

2020-03-29 Thread Vitaly Zuevsky
I have now fixed this bug locally. The leak is in jobtab array (jobs.c). I concluded that the most logical approach would be eliminating inconsistency between makejob() and dowait() functions. My fix in a forked repo:

Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop

2020-03-17 Thread Vitaly Zuevsky
done -- RSS will not grow if precedence is addressed like so: true || (echo &) I interpret it as starting/terminating cycle of a background job is leaky. Br Vitaly -Original Message- From: Andrej Shadura [mailto:and...@shadura.me] Sent: Sunday, March 15, 2020 6:47 PM To

Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop

2020-03-09 Thread Vitaly Zuevsky
Package: dash Version: 0.5.8-2.1ubuntu2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? [VZ]I use a shell script to supervise processes in a docker/kubernetes container. I noticed