From: Max Schulze <max.schulze@online.de>
To: wireguard@lists.zx2c4.com
Subject: wireguard.exe /ui using lots of RAM (>5GB)
Date: Mon, 11 Dec 2023 11:52:09 +0100 [thread overview]
Message-ID: <b0022d92-ce31-4858-aa5d-9b5a6222b733@online.de> (raw)
Hello,
today, I saw a long-running (possibly 90+ days) "wireguard.exe /ui" process using 5Gb of RAM (nearly the limit of the machine). Normal operation is around 14 Mb.
WireGuard/0.5.3 (Windows 10.0.17763; amd64) Using WireGuardNT/0.10
I did a wireguard.exe /dumplog, but it only shows "handshake/keepalive" every two minutes like clockwork.
The wireguard tray Icon was possibly there (empty box) and did not react.
Starting wireguard.exe /ui from the command line did nothing.
I killed the process in windows explorer and restarted.
What can I do next time to gather more useful info?
Best,
M
reply other threads:[~2023-12-11 10:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b0022d92-ce31-4858-aa5d-9b5a6222b733@online.de \
--to=max.schulze@online.de \
--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).