> 0.92.3UL > > It seems to work fine for a while, but after a short time connected will > consume all avaialble ram and swap. Here is an example, with just one > (local) nntp client (slrn) after about 30 minutes of use, at this point I > had to kill nntpcached as the machine was swaping into an early grave. > > news 8716 0.0 0.1 25600 44 p4 S 16:41 0:00 (nntpcached) > news 8747 1.2 78.2 58548 24380 p4 D 16:44 0:14 (nntpcached) It is normaly to see huge memory usages with nntpcached. Around 16 Mb of this is shared memory, of which about 2-5 Mb tends to be used. However from your example something definately appears amis with the child process. I've not seen this behavior myself. Try 0.92.4. > I'm running linux 2.0.17, Libc-5.3.12. Any ideas why this happens, has the > code been tested against purify or similar to see if it has a per article > memory leak? I've been using electric fence to test malloc bounds, but haven't tested for memory leaks. -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+
