unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: djcb@djcbsoftware.nl
Cc: 5535@debbugs.gnu.org
Subject: bug#5535: 23.1.50; emacs daemon high CPU load even while ununsed
Date: Sat, 6 Feb 2010 10:34:18 -0800 (PST)	[thread overview]
Message-ID: <201002061834.o16IYInw028968@godzilla.ics.uci.edu> (raw)
In-Reply-To: <867hqqnyqp.fsf@djcbsoftware.nl> (djcb@djcbsoftware.nl's message of "Sat, 06 Feb 2010 17:57:18 +0200")

djcb@djcbsoftware.nl writes:

  > I noted that Emacs (emacs --daemon) takes a lot of of CPU (up to 80%), even
  > when I am not using it. I am starting emacs --daemon from my ~/.gnomerc, which
  > is invoked when I start my X session.
  > 
  > I used strace to see what was going on:
  > 
  > gettimeofday({1265471350, 42334}, NULL) = 0
  > read(0, "", 4096)                       = 0
  > write(2, "Back to top level.", 18)      = 18
  > write(2, "\n", 1)                       = 1
  > poll([{fd=7, events=POLLIN}], 1, 0)     = 0 (Timeout)
  > gettimeofday({1265471350, 42538}, NULL) = 0
  > read(0, "", 4096)                       = 0
  > write(2, "Back to top level.", 18)      = 18
  > write(2, "\n", 1)                       = 1
  > poll([{fd=7, events=POLLIN}], 1, 0)     = 0 (Timeout)
  > gettimeofday({1265471350, 42736}, NULL) = 0
  > read(0, "", 4096)                       = 0
  > write(2, "Back to top level.", 18)      = 18
  > write(2, "\n", 1)                       = 1
  > 
  > [...]
  > 
  > and this continues at high speed. Apparently, emacs calling the lisp function
  > normal-top-level in lisp/startup.el many, many times.
  
  > Hope this helps tracking down the issue.

Did you have X11 emacs frames and kill the frames, or kill X11?
If yes, then it's probably a long time bug in Gtk+ that causes this.
http://bugzilla.gnome.org/show_bug.cgi?id=85715

  > Best wishes,
  > Dirk.
  > 
  > 
  > If you would like to further debug the crash, please read the file
  > /usr/share/emacs/23.1.50/etc/DEBUG for instructions.
  > 
  > 
  > In GNU Emacs 23.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0)
  >  of 2009-09-27 on crested, modified by Debian
  >  (emacs-snapshot package, version 1:20090909-1)

This is an old snapshot, you might want to try a newer version.






  reply	other threads:[~2010-02-06 18:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06 15:57 bug#5535: 23.1.50; emacs daemon high CPU load even while ununsed djcb
2010-02-06 18:34 ` Dan Nicolaescu [this message]
2010-02-07 15:06   ` Dirk-Jan C. Binnema
2011-10-06  7:40     ` Glenn Morris
2011-10-23 17:52       ` bug#5535: " Dirk-Jan C. Binnema
2011-11-29 11:57 ` bug#5535: 24.0.91, emacs daemon high CPU load and .xsession-errors overflow Sascha Wilde
2011-11-29 12:07   ` Sascha Wilde
2020-08-07 10:52 ` bug#5535: 23.1.50; emacs daemon high CPU load even while ununsed Stefan Kangas
2020-08-08  7:33   ` Dirk-Jan C. Binnema
2020-08-08 14:42     ` Stefan Kangas

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=201002061834.o16IYInw028968@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=5535@debbugs.gnu.org \
    --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).