all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Raeburn <raeburn@permabit.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 17691@debbugs.gnu.org
Subject: bug#17691: 24.3.91; crash closing remote frame
Date: Thu, 7 Aug 2014 02:02:18 -0400	[thread overview]
Message-ID: <B845A36E-CC9A-4293-A8A1-AC0ED53E8575@permabit.com> (raw)
In-Reply-To: <53E30D5B.1040903@cs.ucla.edu>


On Aug 7, 2014, at 01:23, Paul Eggert <eggert@cs.ucla.edu> wrote:

> Ken Raeburn wrote:
>> Yes, the branch now handles my test situation without the excessive CPU use, although it does accumulate file descriptors in CLOSE_WAIT state from the lost X11 connections.
> 
> We should fix that too, I guess.  Does Emacs 24.3 have this file descriptor leak too?  If so, it's not a regression and any fix should be in the trunk.

Yes, the leak appears to be an older problem.

Ken




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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 17:09 bug#17691: 24.3.91; crash closing remote frame Ken Raeburn
2014-06-04 17:34 ` Ken Raeburn
2014-06-04 17:36   ` Ken Raeburn
2014-06-04 17:39 ` Dmitry Antipov
2014-06-04 21:38   ` Ken Raeburn
2014-06-04 21:49     ` Ken Raeburn
2014-06-05  4:53       ` Dmitry Antipov
2014-06-05  5:56         ` Dmitry Antipov
2014-06-05 19:47         ` Ken Raeburn
2014-06-05 21:09           ` Ken Raeburn
2014-06-12 21:14             ` Ken Raeburn
2014-06-13  6:05               ` Eli Zaretskii
2014-06-13 21:37                 ` Ken Raeburn
2014-06-18 22:00 ` Paul Eggert
2014-06-21  2:52   ` Ken Raeburn
2014-06-21 18:21     ` Paul Eggert
2014-06-22  7:03       ` Ken Raeburn
2014-06-22 19:14         ` Paul Eggert
2014-08-02 21:34           ` Paul Eggert
2014-08-07  5:06             ` Ken Raeburn
2014-08-07  5:23               ` Paul Eggert
2014-08-07  6:02                 ` Ken Raeburn [this message]
2014-08-07 12:26                   ` Stefan Monnier
2014-08-07 14:36                     ` Paul Eggert

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=B845A36E-CC9A-4293-A8A1-AC0ED53E8575@permabit.com \
    --to=raeburn@permabit.com \
    --cc=17691@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.