all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 22305@debbugs.gnu.org
Subject: bug#22305: 24.5; permanent 100% CPU load for no apparent reason
Date: Mon, 04 Jan 2016 19:16:46 +0200	[thread overview]
Message-ID: <834met6z9d.fsf@gnu.org> (raw)
In-Reply-To: <41538.98876.177125.22154@gargle.gargle.HOWL> (winkler@gnu.org)

> Date: Mon, 4 Jan 2016 10:48:02 -0600
> From: "Roland Winkler" <winkler@gnu.org>
> 
> Lately emacs gives me some strange problem, where according to `top'
> the CPU load due to the emacs process goes up to a permanent value
> of 100% (and I notice this because the laptop fan starts spinning
> loudly), whereas according to `ps' the emacs process continues to
> give rise to only a marginal CPU load.  While this happens, emacs
> responds normally, so it appears that emacs is not trying to do
> anything unusual in the background.

Not necessarily.  AFAIR, 'top' shows the CPU usage of each program in
terms of processor execution units.  IOW, 100% means Emacs is pegging
a single execution unit.  How many execution units (cores) do you have
on that system?

> What can I do to pin this down further?  So far, I have not noticed
> anything that triggers this behavior reproducibly and my workaround
> has been to restart emacs.  But that's not nice for a recurring
> problem (about once per day).

When this happens, attach a debugger and show us the backtrace,
including the Lisp backtrace.





  reply	other threads:[~2016-01-04 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 16:48 bug#22305: 24.5; permanent 100% CPU load for no apparent reason Roland Winkler
2016-01-04 17:16 ` Eli Zaretskii [this message]
2016-01-04 17:47   ` Roland Winkler
2016-12-07 18:57     ` Glenn Morris
2016-01-04 18:33   ` Michael Heerdegen

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=834met6z9d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22305@debbugs.gnu.org \
    --cc=winkler@gnu.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 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.