On Wed, Jun 27, 2012 at 3:21 PM, Irek Szczesniak <[email protected]> wrote: > On Thu, Jun 21, 2012 at 8:18 AM, Roland Mainz <[email protected]> > wrote: >> Hi! >> >> ---- >> >> Attached (as "bigfilecommandsubstitution001.sh.txt") is a short demo >> which shows a problem in ast-ksh.2012-06-12 with memory usage for >> str="$( < bigfile )" (and similar usage). The problem seems to be that >> a larger input file size (for example 32MB) triggers excessive memory >> usage, usually well beyond 512MB on Solaris 11/AMD64. >> >> Running the demo triggers the following error (this comes from the >> limits defined via "ulimit" in the test (e.g. we assume that a file >> size of 32MB will not cause more than 64MB of extra memory usage in >> ksh93 (ksh93 itself is granted 16MB for itself&&running the script, >> e.g. the ulimit limits are 80MB total in this case. However even that >> is very very generous)): >> -- snip -- >> $ env - LC_ALL=C ~/bin/ksh /tmp/bigmem.sh >> -rw-r--r-- 1 test001 users 33226753 Jun 21 08:10 mytestfile >> bigfilecommandsubstitution001.sh: line 36: storage allocator out of >> space on 8486912 byte request ( region 545751040 segments 133 busy >> 151:8769120:8421280 free 139:536966640:8355744 ) [Not enough space] >> -- snip -- > > We can confirm the bug, and I personally agree that it is a bad one. > I'm sorry we missed that but our machines have a bit more memory than > the usual desktop and even dedicated 1TB+ swap discs. That's why we > missed this.
I tried another test, if I use the current ksh beta in Opensolaris as /bin/sh it won't boot in a VMware VM with just 1GB memory. IMO ksh needs to be fixed before the next official ksh93u+ or that release will be unusable. Irek _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
