On Monday 24 June 2013 16:13:01 Chet Ramey wrote:
> On 6/17/13 1:27 AM, Mike Frysinger wrote:
> > simple test code:
> > unset foo
> > printf -v foo ""
> > echo ${foo+set}
> >
> > that does not display "set". seems to have been this way since the
> > feature was added in bash-3.1.
>
>
On Mon, Jun 24, 2013 at 11:45:19AM -0700, John Reiser wrote:
> > I took a look and saw the bash process consuming as much as 3+ GB of
> > memory. I'm not doing anything where I'd expect to be consuming that
> > much memory.
>
> As a workaround, try using "ulimit -v" to restrict the virtual memo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/17/13 1:27 AM, Mike Frysinger wrote:
> simple test code:
> unset foo
> printf -v foo ""
> echo ${foo+set}
>
> that does not display "set". seems to have been this way since the feature
> was added in bash-3.1.
printf returns
> I took a look and saw the bash process consuming as much as 3+ GB of
> memory. I'm not doing anything where I'd expect to be consuming that
> much memory.
As a workaround, try using "ulimit -v" to restrict the virtual memory
space of the shell itself. (For invoking some child processes, it m
