Re: Memleak with 0.0.20171221-5 on Debian stretch

2018-02-11 Thread Baptiste Jonglez
On 12-02-18, Baptiste Jonglez wrote: > Hi Jason, > > On 12-02-18, Jason A. Donenfeld wrote: > > Secondly, I'm wondering if you tend to do, "anything strange". For > > example -- are you setting up and taking down the device often in an > > automated way? Or reconfiguring the interface (via wg(8),

Re: Memleak with 0.0.20171221-5 on Debian stretch

2018-02-11 Thread Baptiste Jonglez
Hi Jason, On 12-02-18, Jason A. Donenfeld wrote: > Secondly, I'm wondering if you tend to do, "anything strange". For > example -- are you setting up and taking down the device often in an > automated way? Or reconfiguring the interface (via wg(8), for example) > often in an automated way? Or is

Starcraft over Wireguard ... :sideeye:

2018-02-11 Thread Eric Light
Hi, awesome WG mailinglist! My 18 year-old has recently moved out of home, and we're starting to yearn for one of our traditional Starcraft matches. I thought I should be able to do this easily with Wireguard. The idea, generally, is that one of us would start up a game, and Wireguard - with a

Re: Memleak with 0.0.20171221-5 on Debian stretch

2018-02-11 Thread Daniel Kahn Gillmor
On Sun 2018-02-11 19:43:12 +0100, Baptiste Jonglez wrote: > On 11-02-18, Daniel Kahn Gillmor wrote: > >> i'm curious from the graph -- do you know what happened at the start of >> week 6 where there's a sawtooth? > > Actually, the amount of "slab_cache" didn't change at that point, it's > just the

Re: Memleak with 0.0.20171221-5 on Debian stretch

2018-02-11 Thread Jason A. Donenfeld
Hey Baptiste, Thanks for the detailed report. Graphs like that are quite helpful. I'm just back from a long weekend, so sorry for not having a chance to look at this sooner. I'm first curious about the basic "control group" issue Daniel mentioned -- it's probably important to isolate if it's the

Re: Memleak with 0.0.20171221-5 on Debian stretch

2018-02-11 Thread Baptiste Jonglez
On 11-02-18, Daniel Kahn Gillmor wrote: > 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

Re: Memleak with 0.0.20171221-5 on Debian stretch

2018-02-11 Thread Daniel Kahn Gillmor
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,

Memleak with 0.0.20171221-5 on Debian stretch

2018-02-11 Thread Baptiste Jonglez
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