Re: String replacements leak small amounts of memory each time

2010-06-23 Thread Matthew Woehlke
Chet Ramey wrote: On 6/22/10 6:57 PM, Matthew Woehlke wrote: No question something bad is going on here. You're right. I found and fixed it. It wasn't where I was looking initially. The fix will be in the next bash release and may come out as a patch. Also, when run under valgrind, I see

Re: String replacements leak small amounts of memory each time

2010-06-22 Thread Chet Ramey
On 6/22/10 6:57 PM, Matthew Woehlke wrote: > No question something bad is going on here. You're right. I found and fixed it. It wasn't where I was looking initially. The fix will be in the next bash release and may come out as a patch. > Also, when run under valgrind, I see a number of leaks

Re: String replacements leak small amounts of memory each time

2010-06-22 Thread Matthew Woehlke
oyvi...@dhampir.no wrote: Description: When used in a script that iterates over several thousand lines of logs or similar data, the bash string replacement functions seem to leak memory. The Repeat-By list uses "ls -lR" to generate input, but any data will do (try your system logs) Repeat-By:

Re: String replacements leak small amounts of memory each time

2010-06-14 Thread Chet Ramey
On 6/14/10 5:25 PM, Øyvind Hvidsten wrote: > It would seem Debian Squeeze uses that option as default. > Without it, I get a whole ton of warnings, and errors about "free", > "malloc" and "realloc" being defines multiple times. > > Have you tried to reproduce the problem outside of Valgrind? Just

Re: String replacements leak small amounts of memory each time

2010-06-14 Thread Øyvind Hvidsten
It would seem Debian Squeeze uses that option as default. Without it, I get a whole ton of warnings, and errors about "free", "malloc" and "realloc" being defines multiple times. Have you tried to reproduce the problem outside of Valgrind? Just running the examples and looking at the memory us

Re: String replacements leak small amounts of memory each time

2010-06-13 Thread Chet Ramey
On 6/13/10 5:33 PM, Øyvind Hvidsten wrote: > It could be logical leaks, or whatever is the correct english term for > them. Memory that's used, and kept track of, but not used again, and not > freed until the program shuts down. The memory usage is constantly > increasing. I have a process using 3

Re: String replacements leak small amounts of memory each time

2010-06-13 Thread Øyvind Hvidsten
It could be logical leaks, or whatever is the correct english term for them. Memory that's used, and kept track of, but not used again, and not freed until the program shuts down. The memory usage is constantly increasing. I have a process using 3 gigs now, and it just runs one of those testcas

Re: String replacements leak small amounts of memory each time

2010-06-13 Thread Chet Ramey
On 6/13/10 11:17 AM, oyvi...@dhampir.no wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i486 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' > -DC

String replacements leak small amounts of memory each time

2010-06-13 Thread oyvindh
Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba