unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: sit-for
Date: Sat, 29 Jul 2006 10:40:20 +0200	[thread overview]
Message-ID: <85k65wpzwr.fsf@lola.goethe.zz> (raw)
In-Reply-To: <85wt9wq3u1.fsf@lola.goethe.zz> (David Kastrup's message of "Sat, 29 Jul 2006 09:15:34 +0200")

David Kastrup <dak@gnu.org> writes:

> Chong Yidong <cyd@stupidchicken.com> writes:
>
>> David Kastrup <dak@gnu.org> writes:
>>
>>> Since we have the new sit-for implementation, I have a lot of times
>>> when Emacs just pauses in busy waiting for input.  This happens
>>> spontaneously.  One situation where it happens frequently is when
>>> reading news with gnus.
>>
>> I haven't seen this problem in my usage of gnus.
>
> It is not just gnus.  And it is not easy to see: Emacs gets somewhat
> sluggish, sometimes the cursor blinks quite less than expected, and
> CPU usage goes up, up, up, which is of course mostly noticeable when
> you have power management, and the fans start waking up.
>
>> It would be helpful if you could be more specific: does the problem
>> happen with the 2006-07-26 change to `read-event'?
>
> Already before.  I have now recompiled Emacs and will see whether this
> changes something.

Update: it still happens.  I am working for a while in a web browser,
suddenly the fans engage, the Emacs frame (not even mapped when this
happens) shows a very slow and erratically blinking cursor, and `top'
shows that Emacs is consuming close to 100% of CPU power.

So yes, even an off-screen Emacs sitting idle in some frame suddenly
decides to suck up all CPU power.

>> If so, did it start to happen at that time, or did it already
>> happen after the Lisp-level `sit-for' was implemented?
>>
>> If it only started after the `read-event' change, one possibility
>> is that read_char is getting stuck somewhere before we get to the
>> point where we check if the timeout has elapsed.
>>
>>> This is really a nuisance.  The change to sit-for is a fundamental
>>> change to some core mechanism of Emacs, and it is currently
>>> seemingly breaking quite a few things, apart from causing strange
>>> effects.
>>
>> That's the story of the Emacs 22 feature freeze.

I can't remember any change as invasive as that without a
correspondingly bad bug it was trying to fix.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-07-29  8:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 21:06 sit-for David Kastrup
2006-07-28 21:48 ` sit-for Chong Yidong
2006-07-29  7:15   ` sit-for David Kastrup
2006-07-29  8:40     ` David Kastrup [this message]
2006-07-29 14:43       ` sit-for Chong Yidong
2006-07-30 22:36         ` sit-for Kim F. Storm
2006-07-31 18:29           ` sit-for Richard Stallman
2006-07-29 23:34       ` sit-for Richard Stallman
2006-07-29 23:34     ` sit-for Richard Stallman
2006-08-02  0:05     ` sit-for Chong Yidong
2006-08-02  6:09       ` sit-for David Kastrup
2006-08-01 16:38 ` sit-for Chong Yidong
2006-08-01 23:24   ` sit-for Kim F. Storm
2006-08-01 23:52     ` sit-for Chong Yidong
2006-08-02  6:06     ` sit-for David Kastrup
2006-08-03 15:50     ` sit-for Richard Stallman

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=85k65wpzwr.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@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 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).