Eric Knauel <knauel@...> writes:
> Memory consumption still seems to grow while switching between
> workspaces in WindowMaker 0.80.2. However, it grows much slower. After
> a few hours and maybe one houndred switches top says this:
> 25818 XDarwin 0.6% 1:19.47 3 90 580 17.1M 374M 249M 509M
> Right after the start XDarwin used about 120M. Every switch increases
> these numbers by 4M (sometimes a little less).
I can reproduce this with WindowMaker. More details: we're creating
some windows with every switch that never go away. When switching between
empty workspaces, two small windows are created. I suspect one of them is
the "Workspace x" window that is drawn and then fades. More and bigger
windows are created and leaked when switching between non-empty workspaces,
probably duplicates of the existing windows, but I haven't instrumented that
case carefully yet. The large memory leaks reported are probably from
the window buffers of the large windows.
This could be WindowMaker leaking X11 windows, or an XDarwin bug where
Mac OS windows are outliving their X11 counterparts.
I can't reproduce the leaks with fvwm2. If it's an XDarwin bug, it's
peculiar to the sequence of calls used by WindowMaker.
Greg Parker gparker@...
Get latest updates about Open Source Projects, Conferences and News.