zsh-workers
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.org>
To: Bart Schaefer <schaefer@brasslantern.com>,
	zsh-workers@sunsite.dk, 482346@bugs.debian.org
Subject: Re: Bug#482346: zsh doesn't always wait for its children (-> zombie)
Date: Sat, 24 May 2008 14:44:45 +0200	[thread overview]
Message-ID: <20080524124445.GQ7056@prunille.vinc17.org> (raw)
In-Reply-To: <20080524025556.GA30511@scru.org>

severity 482346 important
thanks

On 2008-05-24 02:55:56 +0000, Clint Adams wrote:
> On Sat, May 24, 2008 at 12:43:05AM +0200, Vincent Lefevre wrote:
> > Same problem with zsh-beta 4.3.6-dev-0+20080506-1.
> 
> Just to keep things clear, that has users/12815 applied, and the
> original report did not.

A bit more information:

This is 100% reproducible with both zsh and zsh-beta. This makes
the load average go very high (e.g. up to 26) and ends up by DoS
(the news server complains about the load average and shuts the
connection down). The only solution seems to reboot the machine.
(That's why I've increased the bug severity to important.)

Note: when I kill zsh, the zombie remains there and gets attached
to init. The load average remains very high.

I do not have such a problem when I start vlc from bash and quit
it in the same way.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)


  reply	other threads:[~2008-05-24 12:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080521235008.GA5600@ay.vinc17.org>
     [not found] ` <20080521235930.GW7056@prunille.vinc17.org>
2008-05-22 23:33   ` Clint Adams
2008-05-23 14:39     ` Bart Schaefer
2008-05-23 14:57       ` Clint Adams
2008-05-23 22:43         ` Vincent Lefevre
2008-05-23 22:45           ` Vincent Lefevre
2008-05-23 23:04             ` Vincent Lefevre
2008-05-24  2:55           ` Clint Adams
2008-05-24 12:44             ` Vincent Lefevre [this message]
2008-05-24 14:25               ` Peter Stephenson
2008-05-24 15:27                 ` Stephane Chazelas
2008-05-24 15:58                   ` Stephane Chazelas
2008-05-24 17:53                     ` Clint Adams
2008-05-24 17:41                   ` Bart Schaefer
2008-05-24 18:25                     ` Stephane Chazelas
2008-05-24 23:40               ` Phil Pennock
2008-05-25  0:41                 ` Vincent Lefevre
2008-05-25  1:23                   ` Phil Pennock
2008-05-25 21:37                     ` Vincent Lefevre
2008-05-25 22:26                       ` Phil Pennock
2008-05-25 23:34                         ` Vincent Lefevre
2008-05-25 23:43                           ` Vincent Lefevre
2008-05-26  0:31                           ` Bart Schaefer
2008-05-25 10:08                   ` Stephane Chazelas
2008-05-25 21:54                     ` Vincent Lefevre

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=20080524124445.GQ7056@prunille.vinc17.org \
    --to=vincent@vinc17.org \
    --cc=482346@bugs.debian.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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).