zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Nick Cross <nick@goots.org>, lilydjwg <lilydjwg@gmail.com>,
	zsh-users@zsh.org
Subject: Re: It seems that I find a zle -F full CPU bug
Date: Wed, 16 Jul 2014 09:01:54 -0700	[thread overview]
Message-ID: <140716090154.ZM2509@torch.brasslantern.com> (raw)
In-Reply-To: <53C6845E.7020203@goots.org>

On Jul 16,  2:55pm, Nick Cross wrote:
} Subject: Re: It seems that I find a zle -F full CPU bug
}
} Using Fedora 5.0.5 and similar background code from Bart 
} (http://www.zsh.org/mla/users/2014/msg00448.html) I can see the same 
} POLLNVAL high CPU from strace.
} 
} Is there any suitable workaround for 5.0.5 ?

Unfortunately I don't think there's any shell-language-level workaround.

You could try fiddling with the order in which the zle -F handlers are
removed and skip closing the descriptor in update_super_status, but it
will become complicated to keep track of the un-closed descriptors in
order to avoid leaking (i.e., never closing) them.


  reply	other threads:[~2014-07-16 16:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  5:04 lilydjwg
2014-02-20  7:30 ` Bart Schaefer
2014-02-20  9:40   ` Peter Stephenson
2014-02-20 13:16     ` lilydjwg
2014-07-16 13:55       ` Nick Cross
2014-07-16 16:01         ` Bart Schaefer [this message]
2014-07-16 17:10           ` Nick Cross
2014-07-16 17:50             ` Bart Schaefer
2014-07-17 13:52               ` Nick Cross
2014-07-17 15:52                 ` Dominic Hopf
2014-07-17 17:18                   ` Bart Schaefer
2014-07-17 18:30                     ` Dominic Hopf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=140716090154.ZM2509@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=lilydjwg@gmail.com \
    --cc=nick@goots.org \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).