From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13634 invoked by alias); 30 Oct 2009 21:39:42 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 27321 Received: (qmail 29766 invoked from network); 30 Oct 2009 21:39:30 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received-SPF: none (ns1.primenet.com.au: domain at benizi.com does not designate permitted sender hosts) Date: Fri, 30 Oct 2009 17:29:34 -0400 (EDT) From: "Benjamin R. Haskell" To: zsh-workers@zsh.org Subject: Re: zsh eats 100% CPU with completion in / In-Reply-To: <20091030161027.GL3082@fsst.voodoo.lan> Message-ID: References: <20091030161027.GL3082@fsst.voodoo.lan> User-Agent: Alpine 2.01 (LNX 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 30 Oct 2009, Frank Terbeck wrote: > The subject is not entirely correct. > > Zsh eats 100% CPU on a colleague's laptop if you do this: > % cd / > % cd .. > % ./ > > Happens with the most recent CVS HEAD, too. > That's on linux (debian stable, actually). > > The problem is reproducible on his machine. And it doesn't happen if > you do this: > % cd / > % ./ > > The 'cd ..' is required. > > I cannot reproduce the problem on my system with exactly the same > configuration and with exactly the same zsh version. And I am in fact > using the very same OS (debian stable), too. > > As you can imagine, I am quite puzzled and I don't know how to tackle > this. > > Any hints or suggestions are highly welcome. As a potential source of differences, it might be interesting to see what's mounted in the root directory of each machine. This reminds me of Zsh scanning drives under /cygdrive/ when running under Cygwin. Though I'm not sure how the 'cd ..' plays into it... something relating to changes that dealt with current-directory tracking? (sorry, can't recall specifics -- it was on here or zsh-users within the past three months or so) Best, Ben