Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: fpath+="${(u)fpath[@]}" can hog system
- X-seq: zsh-workers 37824
- From: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: fpath+="${(u)fpath[@]}" can hog system
- Date: Thu, 28 Jan 2016 08:49:06 +0100
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=lts9W+iq2LPD09ieTar38R+tBY+LzMfpM6V9NZ9/pt4=; b=DjnltRLltar8NnISH26IYPu2l0rxtedFFMEwHjvsLfdW8WJKxVnQBCm7i+RMmW81SY 8hOUfGGlUf9GAmcc/WVapHxZCQqCk+wmmuPk1c1aVWoZhtHEID00wLHR7aEZv2PyF5ds iJZuTzEShW6wCT2TiaH4b3/u2oJn7brGfN0t7m3Al86chM354X++wFyN3dMajhthoEa5 gWNaUGnE3oOcidPvwIno4wDYdrYWxbHL5f19Q+C5xIBOMZ7fOhitD5Sil4bdZONm5OHw E3h7QOeqCulhrmPmHPLDZ70qmWbwUqJnnPVOXXThGSbaVboq2E4TrR0pFysIAB60guNT pQ4A==
- In-reply-to: <160127145041.ZM6525@torch.brasslantern.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAKc7PVB6x-Eip=v1ctT_Ehf762MXHgBdxP1d7AwcQKX=B5sg8w@mail.gmail.com> <160127145041.ZM6525@torch.brasslantern.com>
On 27 January 2016 at 23:50, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author