Memleak with 0.0.20171221-5 on Debian stretch
baptiste at bitsofnetworks.org
Tue Feb 13 14:17:59 CET 2018
On 12-02-18, Jason A. Donenfeld wrote:
> Hey Baptiste,
> On Mon, Feb 12, 2018 at 8:42 AM, Baptiste Jonglez
> <baptiste at bitsofnetworks.org> wrote:
> > Actually, now that I talk about it, it's not 100% true: on this system,
> > there is a second wireguard interface that is not currently used (it's
> > provisionned to connect a future router that is not yet deployed).
> > The interesting part: this interface has a single peer which has no
> > endpoint but a persistent keepalive.
It seems to be a valid hypothesis: after I disabled persistent keepalives
on this interface (delete interface, remove persistent keepalive from
configuration, create interface again), memory usage has stopped growing:
> That's a super useful observation! I'm guessing this will fix it:
Nice, thanks! I'm looking forward to testing the next release then.
> I'm still analyzing everything to find other places where I might have
> missed something, but hopefully the above does it.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the WireGuard