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 Harald van Dijk
Hi Vitaly, On 31/03/2020 20:07, Vitaly Zuevsky wrote: I must have confused two concepts: waited process in OS -vs- waited job inside shell interpreter. I am trying to see how it work in practice: # true & false & # [2] + Done(1)false [1] + Done true #

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 Harald van Dijk
On 29/03/2020 23:07, Jilles Tjoelker wrote: On Sun, Mar 29, 2020 at 08:06:31PM +0100, Harald van Dijk wrote: On 29/03/2020 18:54, Vitaly Zuevsky wrote: 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

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

2020-03-29 Thread Jilles Tjoelker
On Sun, Mar 29, 2020 at 08:06:31PM +0100, Harald van Dijk wrote: > On 29/03/2020 18:54, Vitaly Zuevsky wrote: > > 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()

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

2020-03-29 Thread Harald van Dijk
Hi Vitaly, On 29/03/2020 18:54, Vitaly Zuevsky wrote: 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-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
: Vitaly Zuevsky; 953...@bugs.debian.org Cc: Debian Bug Tracking System Subject: Re: Bug#953421: dash: Resident Set Size growth is unbound (memory leak) on an infinite shell loop Thanks for your report; this most likely is a bug in the upstream package. While I doubt it’s any of our patches that in

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

2020-03-15 Thread Andrej Shadura
Hi, On Mon, 9 Mar 2020 at 17:09, Vitaly Zuevsky wrote: > [VZ]I use a shell script to supervise processes in a docker/kubernetes > container. I noticed steady growth > in the cgroup's CPU utilization from 15 to 35 millicores within 17 > days in absence of any external >

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