And can you test with any other window manager (e.g. awesome, dwm, wmii) to see if the issue really is i3 specific please?
On Thu, Jul 23, 2020 at 3:05 AM Gabriel Krisman Bertazi <kris...@collabora.com> wrote: > > Michael Stapelberg <mich...@i3wm.org> writes: > > > Is this fixed with commit > > https://github.com/i3/i3/commit/025743eaf9c993e57c7fdd20127078b835bcd2c0 > > already (not yet released)? Or are we talking about a separate leak? > > Sorry for the delay. > > I built the 4.18 package with this patch, and have been running it for > the past 3 days. The issue persists: > > ❯ ps -o etime= $(pidof Xorg) > 3-05:34:11 > > root@dilma:/home/krisman/src/i3-wm-4.18# cat /proc/$(pidof Xorg)/status | > grep Vm > VmPeak: 5488804 kB > VmSize: 5471796 kB > VmLck: 0 kB > VmPin: 0 kB > VmHWM: 4507732 kB > VmRSS: 4507732 kB > VmData: 4516956 kB > VmStk: 132 kB > VmExe: 1580 kB > VmLib: 116212 kB > VmPTE: 9480 kB > VmSwap: 556 kB > > xrestop doesn't seem bad: > > xrestop - Display: localhost > Monitoring 33 clients. XErrors: 0 > Pixmaps: 102802K total, Other: 56K total, All: 102858K total > > The top entry in xrestop, in particular: > res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier > 0400000 49 91 1 43 412 56925K 13K 56938K ? i3 > > Pixmaps is not increasing over time, even though the overall xorg memory > is. > > -- > Gabriel Krisman Bertazi -- Best regards, Michael
