Huge execution time in 4.2, WAS: for; do; done regression ?
From:
Jan Schampera
Subject:
Huge execution time in 4.2, WAS: for; do; done regression ?
Date:
Fri, 07 Jan 2011 11:09:53 +0100
User-agent:
Mozilla-Thunderbird 2.0.0.24 (X11/20100329)
Alexander Tiurin wrote:
~$ time for i in `seq 0 10000` ; do echo /o/23/4 | cut -d'/' -f2 ; done > /dev/null
To track this a bit, I ran the exact command several times in a Bash
3.2, seeing increasing execution times (40s up to ~2min), as reported.
I knew there were several bugs about filedescriptors and leaks fixed
since then, so I tested it in 4.2 beta. The first run took about 27
minutes(!), the second run still goes on.
I can't imagine this is just some debugging code still active (it's a beta).
Anybody else able to reproduce this?
--
Be conservative in what you do, be liberal in what you accept from others.
- jbp, master of the net, in RFC793