unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: "Dirk-Jan C. Binnema" <djcb@djcbsoftware.nl>, 5386@debbugs.gnu.org
Subject: bug#5386: 23.1.91;
Date: Fri, 15 Jan 2010 09:37:08 -0800 (PST)	[thread overview]
Message-ID: <201001151737.o0FHb8p0016488@godzilla.ics.uci.edu> (raw)
In-Reply-To: <878wbzjosj.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 15 Jan 2010 11:50:04 -0500")

Chong Yidong <cyd@stupidchicken.com> writes:

  > Dirk-Jan C. Binnema <djcb@djcbsoftware.nl> writes:
  > 
  > > I'm using emacs --daemon, and what happens quite often is that when I
  > > log out of my X session and log on as another user, the first user's
  > > daemon hangs around, and after a while start consuming a lot of CPU
  > > (up to 60-70% or more).  Only killing it seems to help.
  > 
  > I'm afraid this looks like a manifestation of Bug#3360, which is related
  > to a long-standing GTK bug.  One way to work around is to compile Emacs
  > without GTK support.

Given that we get this bug report all the time, how about adding a
printf when using --daemon when using the Gtk toolkit that describes the
problem, and gives a pointer to the bug report?
This will make people aware something might happen at the time they start
emacs --daemon. 






  reply	other threads:[~2010-01-15 17:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 20:45 bug#5386: 23.1.91; Dirk-Jan C. Binnema
2010-01-15 16:50 ` Chong Yidong
2010-01-15 17:37   ` Dan Nicolaescu [this message]
2010-01-15 18:07     ` Chong Yidong
2010-01-15 18:13       ` Dan Nicolaescu
2010-01-15 19:21         ` Chong Yidong
2010-01-15 19:31           ` Dan Nicolaescu
2010-01-15 19:41           ` Dirk-Jan C. Binnema
2010-01-15 17:11 ` Jan Djärv

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=201001151737.o0FHb8p0016488@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=5386@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=djcb@djcbsoftware.nl \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).