Re: Examine route.c! (Was: memory leak detector, 2.0.32, patch)

[Chris Adams]

According to Michael O'Reilly <[e-mail]>:
>Daniel Ryde <[e-mail]> writes:
>> On Thu, 4 Dec 1997, Ingo Molnar wrote:
>> > i have tried this script in various combinations, and route.c:1422 has
>> > always ~10 allocations here :( Wondering whats the speciality in your
>> > setup that triggers the bug.
>> 
>> I have a feeling it is timing dependent, since I also have a slightly
>> faster computer (166Mhz / 100Mhz) which I'm unable to reproduce this on,
>> using the same config... Hmm, I might even try to slow it down, did'nt
>> think of that before...
>
>I've got a pentium II 266Mhz, with 256Meg of ram, running news + gated
>(BGP), and it'll leak about 100meg of ram a day. :)
>
>I think the forwarding, or the frequency of route changes may be the
>key. 

I think it is the number or frequency of route changes.  I have problems
on my news server right now, but I also had trouble when I tried
2.0.x>29 on my shell server.  The only thing on them that is out of the
ordinary is gated.  I use it to pick up the OSPF routes of my dialin
pools and such to avoid lots of ICMP redirects (my core router is a
little weak right now).

I am recompiling my kernel right now with the memleak-deluxe and the
route-patch from the list.

With the old patch, so far route.c:1422 currently has over 4MB of
outstanding allocation after 1 day 40 minutes of uptime.
-- 
Chris Adams - [e-mail]
System Administrator - Renaissance Internet Services
I don't speak for anybody but myself - that's enough trouble.