I can't reproduce in Jaunty with the command in #3.
memory use peaks to 110-120MB and remains constant thereafter.
--
bash is not freeing memory of backticked output
https://bugs.launchpad.net/bugs/82123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: bash (Ubuntu)
Status: Confirmed => Triaged
--
bash (feisty) is not freeing memory of backticked output
https://bugs.launchpad.net/bugs/82123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: bash (Ubuntu)
Importance: Undecided => Low
** Also affects: bash (upstream)
Importance: Undecided
Status: Unconfirmed
--
bash (feisty) is not freeing memory of backticked output
https://launchpad.net/bugs/82123
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
** Changed in: bash (Ubuntu)
Status: Unconfirmed => Confirmed
--
bash (feisty) is not freeing memory of backticked output
https://launchpad.net/bugs/82123
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm this on Edgy. If you increase the number of iterations,
the result is more dramatic. In Edgy, it occurs for both syntaxes.
I noticed, however, that memory usage seems to peak. If you repeatedly
run the loop, bashs memory footprint will eventually stop growing.
--
bash (feisty) is n
