Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <160127145041.ZM6525@torch.brasslantern.com>
References: <CAKc7PVB6x-Eip=v1ctT_Ehf762MXHgBdxP1d7AwcQKX=B5sg8w@mail.gmail.com>
 <160127145041.ZM6525@torch.brasslantern.com>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Thu, 28 Jan 2016 08:49:06 +0100
Message-ID: <CAKc7PVBQfay7WU2LTJ1PXPyJ4eqjR2o4KDhE811Tb4DX=x4LHg@mail.gmail.com>
Subject: Re: fpath+="${(u)fpath[@]}" can hog system
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

On 27 January 2016 at 23:50, Bart Schaefer <schaefer@brasslantern.com> wrote:
> Why would you do that?  What's the intended result?

I wrote this by accident and saw my system going high load

> Yeah, if you increase the size (in bytes) of $fpath by 20! (factorial),
> and then make a copy of that, you are going to consume a buttload of
> resources.

It's a typical situation that I cannot submit a bug because it
reproduces in my long scripts but not in short examples. Sadly this
will probably another one for the collection. And in that collection
some might not be actually bugs. fpath+="${(u)fpath[@]}" hogged my
system after single execution (not in loop) in a freshly opened shell,
few times. That's all I can say. Tried this now and it doesn't
reproduce. That said your point about 20! is important, my script
loaded say 18 plugins  each time calling fpath+="${(u)fpath[@]}", so
this is how all the topic happened, and possibly it wasn't a bug...
Probably the only way to use such reports is taking a glance at
related source code and luckily noticing something

Best regards,
Sebastian Gniazdowski