Re: Latest emacs snapshots max CPU on XP

[Chris McMahan <first_initiallastname@one.dot.net>]

Outstanding! Fixed the problem right away

Thanks!

- Chris McMahan

neverov_dg@nkmk.ru writes:

> Hi!
>
> I had the same problem.
>
> Try to put this in your .emacs:
>
> (setq semantic-idle-scheduler-idle-time 432000)
>
> I found it in the CEDET mail list.
>
>> I found the problem!!
>
>> After commenting and uncommenting various pieces of my various
>> configuration files (many MANY configuration files :)
>
>> The CPU hog was the CEDET library I was using for my ECB installation.
>> Apparently the semantic parser was going wild with the new version.
>> I've disabled the CEDET and ECB packages until I can track down the
>> actual culprit. There's been no update for some time in CEDET, so I
>> may look for alternatives for java programming.
>
>> In the meantime, I'm switching from gnuserv to emacsclient. Thanks for
>> all of your help!
>
>> - 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
>>>
>>>
> ----
> Dmitry
>
>
>
>
>

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