all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris McMahan <first_initiallastname@one.dot.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Latest emacs snapshots max CPU on XP
Date: Thu, 01 Mar 2007 09:10:07 -0500	[thread overview]
Message-ID: <ufy8pgim8.fsf@one.dot.net> (raw)
In-Reply-To: mailman.229.1172692107.7795.help-gnu-emacs@gnu.org

Thanks for the idea, but that didn't seem to have an effect. I'm
thinking that maybe there was an imcompatiblity between the gnuclient
application I was using to launch it and the newer emacs. When I
launch emacs from the runemacs.exe application directly, I don't see
that problem.

I still haven't tracked it down, but it might be related
to attempting to read in from sockets for the gnuserv (a wild guess on
my part :)

- Chris

"Juanma Barranquero" <lekktu@gmail.com> writes:

> On 2/28/07, Chris McMahan <first_initiallastname@one.dot.net> wrote:
>
>> I've used pre-compiled XP binaries and compiled my own using MinGW,
>> and both will suddenly start using up 60-80% of my CPU resources. I've
>> not been able to correlate any specific activities with this behavior.
>
> Could you please try adding
>
>  (setq jit-lock-stealth-time nil)
>
> to your .emacs and report whether it helps?
>
>> The pre-compiled version I'm currently using does not have this
>> problem
>> - GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600) of 2006-06-04 on TPAD
>
> There's quit a lot of changes between that version and the current
> pretest. When did you start to notice the problem?
>
> Do you load many buffers, particularly many buffers with complex
> fontification (source code, etc.)?
>
>             Juanma
>
>

-- 
     (.   .)
  =ooO=(_)=Ooo=====================================
  Chris McMahan | first_initiallastname@one.dot.net
  =================================================

  parent reply	other threads:[~2007-03-01 14:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 19:33 Latest emacs snapshots max CPU on XP Chris McMahan
2007-02-28 19:48 ` Juanma Barranquero
     [not found] ` <mailman.229.1172692107.7795.help-gnu-emacs@gnu.org>
2007-03-01 14:10   ` Chris McMahan [this message]
2007-03-01 15:13     ` Juanma Barranquero
     [not found]     ` <mailman.256.1172762018.7795.help-gnu-emacs@gnu.org>
2007-03-01 17:36       ` Chris McMahan
2007-03-01 20:43         ` Juanma Barranquero
2007-03-01 18:29     ` Eli Zaretskii
     [not found]     ` <mailman.265.1172773775.7795.help-gnu-emacs@gnu.org>
2007-03-01 18:38       ` Chris McMahan
2007-03-01 20:48         ` Juanma Barranquero
2007-03-01 19:55   ` Chris McMahan
2007-03-02  1:09     ` Re[2]: " neverov_dg
     [not found]     ` <mailman.288.1172797775.7795.help-gnu-emacs@gnu.org>
2007-03-03 12:57       ` Malte Spiess
2007-03-03 22:34         ` RealityMonster
2007-03-04  0:14       ` Chris McMahan

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=ufy8pgim8.fsf@one.dot.net \
    --to=first_initiallastname@one.dot.net \
    --cc=help-gnu-emacs@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.