From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-30817-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 24105 invoked by alias); 22 Nov 2012 18:29:57 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 30817
Received: (qmail 21635 invoked from network); 22 Nov 2012 18:29:47 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <121122102927.ZM8049@torch.brasslantern.com>
Date: Thu, 22 Nov 2012 10:29:27 -0800
In-reply-to: <20121122092847.GA2576@localhost.localdomain>
Comments: In reply to Han Pingtian <hanpt@linux.vnet.ibm.com>
 "Re: argv subscript range uses too many memory" (Nov 22,  5:28pm)
References: <20121108084001.GA7594@localhost.localdomain>
	<20121108100226.575b0788@pwslap01u.europe.root.pri>
	<20121110105811.GA7136@localhost.localdomain>
	<121110065709.ZM4781@torch.brasslantern.com>
	<20121120130457.GD2500@localhost.localdomain>
	<121120090300.ZM5552@torch.brasslantern.com>
	<121120094443.ZM5584@torch.brasslantern.com>
	<121120102415.ZM5635@torch.brasslantern.com>
	<20121122092847.GA2576@localhost.localdomain>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: argv subscript range uses too many memory
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Nov 22,  5:28pm, Han Pingtian wrote:
}
} I have tried this patch. Looks like with this patch on 5.0, [loops]
} will run very slow, but the memory problem is solved at the
} sametime.

If you would not mind, try removing both that patch and the one you
previously removed for 29175, but increase HEAPSIZE to

#define HEAPSIZE (163840 - H_ISIZE)

and see if that makes any noticeable difference in the "run very slow"
condition?