Hi all,
please Cc me on ansers as I am not on the list.
I think I found a severe memleak in bash.
I had this effect with bash 4.2.10 (Ubuntu Linux) as well as
bash 4.1.9 on Gentoo Linux.
To make it short:
echo {0..1000}>/dev/null
This makes my system starting to swap as bash will use sev
Hi all,
I think there is a severe memleak in bash.
I had this effect with bash 4.2.10 (Ubuntu Linux) as well as
bash 4.1.9 on Gentoo Linux.
To make it short:
echo {0..1000}>/dev/null
This makes my system starting to swap as bash will allocate several GiB of
memory.
If I choose a way bigg
* Chet Ramey schrieb am 30.11.11 um 14:23 Uhr:
> > Hi all,
> >
> > I think there is a severe memleak in bash.
>
> It's not a memory leak. It might reveal a sub-optimal memory allocation
> pattern -- asking for an array with that many strings is going to gobble
> a lot of memory -- but it's not a
* Greg Wooledge schrieb am 30.11.11 um 14:28 Uhr:
> On Wed, Nov 30, 2011 at 12:37:36AM +0100, Marc Schiffbauer wrote:
> > echo {0..1000}>/dev/null
> >
> > This makes my system starting to swap as bash will use several GiB of
> > memory.
>
> Brace expan
* Chet Ramey schrieb am 01.12.11 um 02:54 Uhr:
> That's probably the result of the power-of-two allocation policy in the
> bash malloc. When this came up before, I wrote:
>
> ==
> That's not a memory leak. Malloc implementations need not release
> memory back to the kernel; the bash mall
* Bob Proulx schrieb am 01.12.11 um 05:34 Uhr:
> Marc Schiffbauer wrote:
> > Greg Wooledge schrieb:
> > > Marc Schiffbauer wrote:
> > > > echo {0..1000}>/dev/null
> > > >
> > > > This makes my system starting to swap as bash will use
