Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: X11R4 Xsun server appears to have a
Message-ID: <9002081441.AA00241@expire.lcs.mit.edu>
Date: 8 Feb 90 14:41:29 GMT
References: <26900100@m.cs.uiuc.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 12


    I got it to grow from about 720 to 888 (with a max of 1016) simply
    by moving already existing windows around.

That by itself is not an indication of a memory leak.  Moving windows around,
most particularly when nonrectangular windows are on the screen, is not a free
operation, the server is maintaining various kinds of region descriptions, and
as you move windows those regions can get more complicated.  You also generate
exposure events, which can potentially cause more output buffers to be
allocated (depends on previous history).  If you have backing-store enable
anywhere, that can also cause memory allocation.  I don't see anything
particularly alarming in those numbers, per se.