Memleak with 0.0.20171221-5 on Debian stretch

Daniel Kahn Gillmor dkg at
Sun Feb 11 19:20:14 CET 2018

Hi Baptiste--

On Sun 2018-02-11 14:48:37 +0100, Baptiste Jonglez wrote:

> On a x86_64 VM with quite a lot of Wireguard traffic (~300 GB per day), I
> am seeing a memory leak with wireguard 0.0.20171221-5.  System is Debian
> stretch, kernel 4.9.65-3+deb9u2, wireguard package from unstable.

oof, thanks for this report, and for the really useful graph

it's troubling that the changes correlated with the memleak are both a
kernel upgrade *and* a wireguard upgrade, since that kind of conflation
might be difficult to tease apart.

i'm curious from the graph -- do you know what happened at the start of
week 6 where there's a sawtooth?

If you still see a leak with the latest wireguard, i'd appreciate if you
could test the current kernel with 0.0.20171011-1 to see whether you can
isolate the problem to the kernel.  i'm not recommending running
0.0.20171011-1 for the long term, but it should still be wire-format
compatible with other implementations and will help with debugging to
have the comparison.



More information about the WireGuard mailing list