From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11871 Path: main.gmane.org!not-for-mail From: Loren Schall Newsgroups: gmane.emacs.gnus.general Subject: 4000000 unread articles Date: 12 Aug 1997 15:44:15 -0700 Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.103) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035151510 505 80.91.224.250 (20 Oct 2002 22:05:10 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:05:10 +0000 (UTC) Return-Path: Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by altair.xemacs.org (8.8.6/8.8.6) with ESMTP id TAA01013 for ; Tue, 12 Aug 1997 19:50:35 -0700 Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id SAA04744 for ; Tue, 12 Aug 1997 18:28:37 -0500 (CDT) Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Wed, 13 Aug 1997 00:43:45 +0200 Original-Received: (qmail 3389 invoked by uid 504); 12 Aug 1997 22:43:44 -0000 Original-Received: (qmail 3386 invoked from network); 12 Aug 1997 22:43:43 -0000 Original-Received: from saifr00.ateng.az.honeywell.com (129.239.166.12) by claymore.vcinet.com with SMTP; 12 Aug 1997 22:43:43 -0000 Original-Received: from swtech09.ateng.az.honeywell.com (swtech09.ateng.az.Honeywell.COM [129.239.1.79]) by saifr00.ateng.az.honeywell.com (8.6.10/8.6.4) with ESMTP id PAA16904 for ; Tue, 12 Aug 1997 15:44:17 -0700 Original-Received: (schall@localhost) by swtech09.ateng.az.honeywell.com (8.6.10/8.6.4) id PAA23725; Tue, 12 Aug 1997 15:44:16 -0700 Original-To: ding@gnus.org Original-Lines: 42 X-Mailer: Gnus v5.4.62/Emacs 19.34 Xref: main.gmane.org gmane.emacs.gnus.general:11871 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11871 I ran into an interesting anomaly this last week. It had been a few days since I'd last read news so when I brought up Gnus, I pushed it to the back. NoCeM usually takes a few minutes to run. Over the next hour or so I checked it occasionally, still running. About an hour and a half after I'd started it, I notices emacs had crashed. I don't remember the error message, but something lead me to believe Emacs had run out of resources. So I restarted Emacs and Gnus, assuming it would start up from where it had left off and finish. About an hour later I noticed it had crashed a again, in NoCeM. So I disabled NoCeM and started things up again. This time I got all the way to my topic buffer. I saw that a lot of groups have more than 3,000,000 unread message, a couple more than 4,000,000. I didn't really think much of it. I'd seen large jumps in article numbers from this NNTP server before. Not this big, but... I wasn't surprised. Before, I'd just enter each group, and after a short pause, discover that the real number of new articles was something more reasonable. I was surprised to find a mail message from my service provide, that they had terminated my emacs process, twice, because it was using too many resources. 150M of virtual memory and 45% of the CPU. Somewhere in the Info files, I found a note that NoCeM was a memory hog, so I hand munged ~/News/NoCeM/active, before reactivating NoCeM. Everything seem to be back to normal. A few days later, I wanted to look at some old articles. When I entered the group I didn't get a summary buffer right away. Oh, I thought, this must be one of those groups with the bogus articles numbers. It'll take a couple of minutes. I pushed my emacs window to the back and did some other stuff for a few minutes. When I returned, my service provider had killed emacs again. Any suggestions? I'm not afraid to dink with the code, if somebody'll tell me where to look. There aren't really 4,000,000 unread articles, but Gnus (and tin and pine, according to my service provider) seem to be expecting articles from 1 to whatever. Is this a limitation of NNTP? -- Loren Schall schall@ateng.az.honeywell.com