* PGnus0.69 is eating away my memory?
@ 1999-01-05 22:42 Robin S. Socha
1999-01-05 22:47 ` Hrvoje Niksic
0 siblings, 1 reply; 6+ messages in thread
From: Robin S. Socha @ 1999-01-05 22:42 UTC (permalink / raw)
Hi,
I'm running XEmacs 21.2 Artemis and PGnus 0.69. Three times today, Gnus has
sucked up all my memory. I guess... ;-) Is there any way I could find out
what's going on?
Robin
--
Robin S. Socha <http://socha.net/>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PGnus0.69 is eating away my memory?
1999-01-05 22:42 PGnus0.69 is eating away my memory? Robin S. Socha
@ 1999-01-05 22:47 ` Hrvoje Niksic
1999-01-15 19:06 ` Robin S. Socha
0 siblings, 1 reply; 6+ messages in thread
From: Hrvoje Niksic @ 1999-01-05 22:47 UTC (permalink / raw)
"Robin S. Socha" <robin@socha.net> writes:
> I'm running XEmacs 21.2 Artemis and PGnus 0.69. Three times today,
> Gnus has sucked up all my memory. I guess... ;-)
What were the exact symptoms that you observed?
If XEmacs has thrown a "not enough memory" error, you can set
`debug-on-error' to t, and mail us the backtrace.
If XEmacs has locked up on you, you can set `debug-on-quit' to t,
press C-g, and mail us the resulting backtrace.
> Is there any way I could find out what's going on?
See above.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PGnus0.69 is eating away my memory?
1999-01-05 22:47 ` Hrvoje Niksic
@ 1999-01-15 19:06 ` Robin S. Socha
[not found] ` <m3pv8gntpi.fsf@peorth.gweep.net>
0 siblings, 1 reply; 6+ messages in thread
From: Robin S. Socha @ 1999-01-15 19:06 UTC (permalink / raw)
* Hrvoje Niksic <hniksic@srce.hr> writes:
> "Robin S. Socha" <robin@socha.net> writes:
[some testing later...]
>> I'm running XEmacs 21.2 Artemis and PGnus 0.69. Three times today, Gnus
>> has sucked up all my memory. I guess... ;-)
> What were the exact symptoms that you observed?
1. Gnus starts *two* instances of leafnode
2. leafnode becomes *huge*
Like this:
robin@radioactive:/home/robin > top
Mem: 63004K av, 55208K used, 7796K free, 14892K shrd, 4940K buff
Swap: 80320K av, 12888K used, 67432K free 14620K cached
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
24970 news 0 0 1992 1992 324 S 0 0.0 3.1 0:00 leafnode
24975 news 0 0 1992 1992 324 S 0 0.0 3.1 0:00 leafnode
However, this can happen, too:
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
272 robin 1 0 25288 19M 3976 S 0 0.0 31.9 20:06 xemacs
315 news 0 0 21976 10M 160 S 0 0.0 17.3 0:17 leafnode
303 news 0 0 21260 8960 140 S 0 0.0 14.2 0:13 leafnode
> If XEmacs has locked up on you, you can set `debug-on-quit' to t, press
> C-g, and mail us the resulting backtrace.
It's obviously not an XEmacs problem. And theoretically, it's not a leafnode
problem, either (this happens with both 1.8 as well as 1.8.2 which Cornelius
Krasel kindly sent me for testing this). leafnode itself doesn't fork (there
is one in fetch.c):
fetch.c: if ( fork() <= 0 ) {
fetch.c: syslog( LOG_DEBUG, "Process forked." );
radioactive:/var/spool/news/leaf.node # cat groupinfo | wc -l
16531
Ummm... does that help a little more?
Robin
--
Robin S. Socha <https://socha.net/>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PGnus0.69 is eating away my memory?
[not found] ` <m3pv8gntpi.fsf@peorth.gweep.net>
@ 1999-01-15 22:25 ` Robin S. Socha
1999-01-15 23:25 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 6+ messages in thread
From: Robin S. Socha @ 1999-01-15 22:25 UTC (permalink / raw)
* Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> Robin S Socha <robin@socha.net> writes:
>> 1. Gnus starts *two* instances of leafnode
> What is the value of `gnus-asynchronous'. When it is non-nil, Gnus opens
> a second NNTP connection to pre-fetch articles.
`gnus-asynchronous' is a variable declared in Lisp.
Value: nil
>> 2. leafnode becomes *huge*
> That I do not know. Maybe a bug in leafnode?
The author doubts that. It happens with lesser versions of leafnode, too,
but it doesn't happen with Gnus-5.6.45 or something.
Am I the only one using this combination and experiencing this? Maybe it's
time to set up INN again }:->
--
Robin S. Socha <https://socha.net/>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PGnus0.69 is eating away my memory?
1999-01-15 22:25 ` Robin S. Socha
@ 1999-01-15 23:25 ` Lars Magne Ingebrigtsen
1999-01-17 0:16 ` Robin S. Socha
0 siblings, 1 reply; 6+ messages in thread
From: Lars Magne Ingebrigtsen @ 1999-01-15 23:25 UTC (permalink / raw)
"Robin S. Socha" <robin@socha.net> writes:
> >> 2. leafnode becomes *huge*
>
> > That I do not know. Maybe a bug in leafnode?
>
> The author doubts that.
Do the leafnode logs (if you switch them on) say anything of interest?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PGnus0.69 is eating away my memory?
1999-01-15 23:25 ` Lars Magne Ingebrigtsen
@ 1999-01-17 0:16 ` Robin S. Socha
0 siblings, 0 replies; 6+ messages in thread
From: Robin S. Socha @ 1999-01-17 0:16 UTC (permalink / raw)
* Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> "Robin S. Socha" <robin@socha.net> writes:
>> >> 2. leafnode becomes *huge*
>> > That I do not know. Maybe a bug in leafnode?
>> The author doubts that.
> Do the leafnode logs (if you switch them on) say anything of interest?
Nope. The author thinks that Gnus is expecting something different from HEAD,
BODY and ARTICLE commands than what leafnode delivers. But - he also says
that he's fixed it for the next version of leafnode.
Robin
--
Robin S. Socha <https://socha.net/>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-01-17 0:16 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-01-05 22:42 PGnus0.69 is eating away my memory? Robin S. Socha
1999-01-05 22:47 ` Hrvoje Niksic
1999-01-15 19:06 ` Robin S. Socha
[not found] ` <m3pv8gntpi.fsf@peorth.gweep.net>
1999-01-15 22:25 ` Robin S. Socha
1999-01-15 23:25 ` Lars Magne Ingebrigtsen
1999-01-17 0:16 ` Robin S. Socha
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).