On Wed, Apr 18, 2018 at 09:57:16AM +0200, Willy Goiffon wrote:
> Le 2018-04-17 14:27, Alexander Demenshin a écrit :
> > On 2018-04-17 13:31, wi...@mailoo.org wrote:
> >
> > > As I said, the mem leak does not apppear in the `birdc show memory`
> > > command.
> > > It is shown at the OS level, and is shown via the `free` command.
> >
> > What do you mean by "OS level"? Which exactly level? What is the actual
> > process
> > size as reported by ps ("ps axuw|grep bird")?
>
> By "OS Level" I mean the memory used as reported by the kernel from
> /proc/meminfo.
Hi
Just curios, which field in /proc/meminfo (or /proc/slabinfo)
is increasing?
> > If ps shows size similar to what you see in birdc "show mem", then the
> > leak
> > is definitely not in bird (though it may be related) - it is in kernel
> > or some other process.
>
> It might not be in bird, but it is definitely triggered by it.
That is interesting, one could imagine that difference between running
BIRD and just using static routes would be that periodic scans could
trigger some kernel bug, but that would cause linear increase independent
of network traffic.
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
