[1122] in SIPB bug reports
GRIPE about XRN 6.9 (for X11R4)
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Sun Jun 24 12:59:54 1990
Date: Sun, 24 Jun 90 00:37:49 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: hindmost@ATHENA.MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: hindmost@ATHENA.MIT.EDU's message of Sat, 23 Jun 90 23:34:23 -0400 <9006240334.AA08844@M11-116-9.MIT.EDU>
I don't know why it takes up so much memory -- I didn't write it.
Seriously, there are two reasons. First of all, it's an X toolkit
program, and X toolkit programs tend to take up a lot of memory (just
for kicks, take a look at how much memory xclock takes up -- can you
believe that something that simple takes up so much memory?).
Second, I believe that there is a slow memory leak in the program.
This means that the longer you leave it running, the more memory it
takes up. The way to get around this is not to leave it running for a
long period of time (more than a couple of hours at a time) -- quit
and restart it periodically.
Also, note that the more unread news you have each time you run it,
the more memory it takes up. Therefore, when you haven't read news
for a long time, it takes more memory to run it than when you keep
up-to-date.
If you've got so much unread news that it refused to even start up,
you can get around this by manually editing your .newsrc to
unsubscribe to some of the newsgroups with the most traffic (by
substituting '!' for ':' on their lines in the .newsrc) until you're
able to run it, then after you've caught up on some of the news,
resubscribe to those groups.
Hope this helps.
--> Jonathan Kamens
Project Athena Watchmaker and User Consultant
Student Information Processing Board (SIPB) member
jik@Athena.MIT.EDU
