Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: wireguard@lists.zx2c4.com
Subject: Memleak with 0.0.20171221-5 on Debian stretch
Date: Sun, 11 Feb 2018 14:48:37 +0100	[thread overview]
Message-ID: <20180211134837.GC12558@lud.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 956 bytes --]

Hi,

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.

I have attached the memory usage reported by Munin over one month.  The
memleak is quite evident, and seems to happen in "slab_cache".  I realized
the issue today because the machine was completely unusable ("fork: cannot
allocate memory" with any command in a shell).

The machine was rebooted just at the point marked "Week 03" (for the
kernel upgrade for Meltdown, but wireguard was also upgraded), and it also
marks the beginning of the memleak.

To sum things up:

- no memleak: kernel 4.9.51-1, wireguard 0.0.20171011-1
- memleak: kernel 4.9.65-3+deb9u2, wireguard 0.0.20171221-5
- currently testing: kernel 4.9.65-3+deb9u2, wireguard 0.0.20180202-1

I will let you know if the memleak is still here with 0.0.20180202-1.

Baptiste

[-- Attachment #1.2: memory-month-zopfli.png --]
[-- Type: image/png, Size: 27099 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-02-11 13:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 13:48 Baptiste Jonglez [this message]
2018-02-11 18:20 ` Daniel Kahn Gillmor
2018-02-11 18:43   ` Baptiste Jonglez
2018-02-12  0:23     ` Jason A. Donenfeld
2018-02-12  7:35       ` Baptiste Jonglez
2018-02-12  7:42         ` Baptiste Jonglez
2018-02-12 11:04           ` Jason A. Donenfeld
2018-02-13 13:17             ` Baptiste Jonglez
2018-02-18 20:39               ` Jason A. Donenfeld
2018-02-22  7:45                 ` Baptiste Jonglez
2018-02-12  3:34     ` Daniel Kahn Gillmor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180211134837.GC12558@lud.localdomain \
    --to=baptiste@bitsofnetworks.org \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).