Re: High CPU load

[YAMAMOTO Mitsuharu]

>>>>> On Tue, 27 Nov 2007 16:29:34 +0000, David Reitter 
>>>>> <david.reitter@gmail.com> said:

>> Does this happen also on unmodified Carbon Emacs, or Aquamacs Emacs
>> only?

> I don't know. Seiji, did you get any reports?

Ah, I meant bare CVS version.  Carbon Emacs Package is also a modified
Carbon Emacs.

>>>>> On Tue, 27 Nov 2007 17:57:54 +0000, David Reitter 
>>>>> <david.reitter@gmail.com> said:

> On 27 Nov 2007, at 13:06, YAMAMOTO Mitsuharu wrote:
>> I have no idea.  Could you try replacing mac.c with the one in the
>> trunk (Rev. 1.84) to see if this changes the situation?

> OK, having done that, I've got a report from a user who still  
> experiences the problem:

> Begin forwarded message:

>> From: Ugur Ozdemir <uozdemir@artsci.wustl.edu>
>> Date: 27 November 2007 17:51:16 GMT
>> To: Development of Aquamacs Emacs <aquamacs-devel@aquamacs.org>
>> Subject: Re: [Aquamacs-devel] Aquamacs / CPU Load Problem
>> Reply-To: Development of Aquamacs Emacs <aquamacs-devel@aquamacs.org>
>> 
>> David,
>> 
>> I had the same problem with this latest nightly build. I do not know
>> these things very much here are the threads that go crazy in the
>> thread viewer:
>> 
>> thr 05807    select$DARWIN_EXTSN
>> -pthread_start
>> thread_start
>> 
>> thr 05c07    mach-msg-trap
>> CFRunLoopRunSpecific
>> CFRunLoopRun
>> TSystemNotificationTask::SystemNotificationTaskProc(void*)
>> PrivateMPEntryPoint
>> -pthread_start
>> thread_start

Thanks for testing.

The second thread seems to be spawned when one uses the file dialog on
Leopard.  Carbon's Navigation Services (file dialogs) have heavily
changed on Leopard so it uses Cocoa's NSSavePanel/NSOpenPanel (you can
see the difference by typing `/' or `~').  So I suspect some bugs have
been introduced there.  Maybe you can avoid this situation by setting
use-dialog-box to nil in the meanwhile.

I also guess high CPU usage has something to do with filesystems over
network, because SystemNotificationTaskProc above seems to monitor
file system volume and the socket monitor thread (the first thread
above) is also busy.  Maybe you can monitor network packets while high
CPU load is observed.

                                     YAMAMOTO Mitsuharu
                                mituharu@math.s.chiba-u.ac.jp