[Olsr-dev] [OLSRd 0000047]: memory leak on one remote end of point to point link

Henning Rogge (spam-protected)
Sat Nov 15 09:48:24 CET 2014


I just had a look at the syslog again and I think there are quite a
few "interface added/removed" messages in this... is this normal on
the other "not memory leeking" node too?

Henning Rogge

On Fri, Nov 14, 2014 at 10:30 AM, Jernej Kos <(spam-protected)> wrote:
> Hello!
> On 14. 11. 2014 10:22, Henning Rogge wrote:
>> just to be absolutely sure, you verified that its olsrd that consumes
>> the storage, right?
> Valent did the checks, he said that the size of the virtual memory
> allocated for the olsrd process is constantly rising and causes the node
> to go out of memory if left unchecked.
> Note that we are only seeing this behaviour on this one node.
>> hmm, is there a computer with a little bit more storage attached to
>> the node with the memory leak? If yes we could maybe take a longer
>> binary tcpdump and replay it to an olsrd with a valgrind attached (I
>> don't think we can run valgrind on your node).
> No, I think that valgrind would not fit on this node. As far as a
> computer with more storage goes, Valent should be able to answer that.
> Jernej

More information about the Olsr-dev mailing list