Just ran into this. I think it should be considered a bug.
Bash is currently holding onto 4.8 GiB of my memory, and when I try to
run less or top it just states "bash: fork: Cannot allocate memory".
Running a large for-loop should not make bash hold onto this much memory
for its whole session.
-
Sorry, Launchpad said it wasn't able to post the comment...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/82123
Title:
bash is not freeing memory of backticked output
To manage notifications about
Just ran into this. I think it should be considered a bug.
Bash is currently holding onto 4.8 GiB of my memory, and when I try to
run less or top it just states "bash: fork: Cannot allocate memory".
Running a large for-loop should not make bash hold onto this much memory
for its whole session.
-
Just ran into this. I think it should be considered a bug.
Bash is currently holding onto 4.8 GiB of my memory, and when I try to
run less or top it just states "bash: fork: Cannot allocate memory".
Running a large for-loop should not make bash hold onto this much memory
for its whole session.
-
Just ran into this. I think it should be considered a bug.
Bash is currently holding onto 4.8 GiB of my memory, and when I try to
run less or top it just states "bash: fork: Cannot allocate memory".
Running a large for-loop should not make bash hold onto this much memory
for its whole session.
-
even if dash seems to be able to do this more efficiently and memory
does not get reassigned until bash exits, I will close this now for the
following reasons. As always, feel free to reopen if you have something
to add or disagree and want some further discussion.
I talked extensively with some
Hmm, I would've thought that "peaking" was okay. I'm not sure, and I'm
just asking out of curiosty: if you malloc a 100MB and something else
has been added to the heap later, it might be possible that the heap
gets fragmented, and that might explain why it simply peaks. In my
original bug report, I
Scott, I must have mixed things up in my head. Your comment 1 already
states that you were essentially seeing the effects that I was seeing.
Just ignore my request for more infomration from you.
--
bash is not freeing memory of backticked output
https://bugs.launchpad.net/bugs/82123
You received
Arnold, Scott mentioned in comment 1 that memory consumption eventually
peaks. Does the memory get freed after the loop ends or only once you
close the bash session? What kind of memory consumption do you see for
for j in $(seq 1 10); do echo "Loop $j"; for i in $(seq 1 100); do
true ; done;
** Summary changed:
- bash (feisty) is not freeing memory of backticked output
+ bash is not freeing memory of backticked output
--
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, wh
10 matches
Mail list logo
