From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/4385 Path: news.gmane.org!not-for-mail From: Christian Lynbech Newsgroups: gmane.emacs.gnus.user Subject: Re: Duration of gnus-change-server Date: Thu, 27 Jan 2005 16:00:45 +0100 Organization: Ericsson Message-ID: <86vf9igbmq.fsf@lapchly.ted.ericsson.se> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138670319 23025 80.91.229.2 (31 Jan 2006 01:18:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:18:39 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:33:41 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!uio.no!npeer.de.kpn-eurorings.net!newsfeed00.sul.t-online.de!t-online.de!frankfurt2.telia.de!newspeer2.se.telia.net!se.telia.net!ltu.se!luth.se!193.180.251.40.MISMATCH!erinews.ericsson.se!news.ericsson.se!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: upl5127.uab.ericsson.se Original-X-Trace: newstree.wise.edt.ericsson.se 1106837760 26342 134.138.113.127 (27 Jan 2005 14:56:00 GMT) Original-X-Complaints-To: abuse@ericsson.se Original-NNTP-Posting-Date: Thu, 27 Jan 2005 14:56:00 +0000 (UTC) User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux) Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:4526 Original-Lines: 22 X-Gnus-Article-Number: 4526 Tue Jan 17 17:33:41 2006 Xref: news.gmane.org gmane.emacs.gnus.user:4385 Archived-At: >>>>> "Michael" == Michael Welle writes: Michael> Gnus is running for 16 hours now, consuming 100% cpu with a constant Michael> memory footprint. I am subscribed to about 40 groups and using a 1.2 MHz Michael> x86 machine. Presumably, your emacs process is toasted. It happens once in a while, later emacs versions is not entirely as robust as they used to be. Try taking a look on the process with strace, you may find that emacs is in rather tight loop apparently doing nothing else but calling gettimeofday or something similar. You can try hitting C-g which may break out of whatever emacs is doing, but it may also very well be that you need to kill the process and start a fresh emacs. Another variation is that emacs is hanging on some "futex" call but then it hangs and you would not see the CPU consumption that you are seeing. -- Christian