Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!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 memory leak
Message-ID: <9002021415.AA09140@expire.lcs.mit.edu>
Date: 2 Feb 90 14:15:55 GMT
References: <4Zm4u6z0-csm9fxMwS@sparc01>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 18


    It also happens with the R4 xlock, I discovered.

I started up a vanilla R4 server on my Sun 3/60 under xinit, with an
xterm, an xclock -update 5, and a twm running with your stated xlock
menu entry installed.  I played around a bit, invoked the R4 xlock
several times via the menu entry, and saw no size increase.  I then
invoked xlock via the menu entry, and went home.  Size before I went
home: 352K.  Size after 12 hours: 352K.  I see no leak here.

I won't swear there isn't a leak, but I'll need more information
about your environment to reproduce it.  On a wild guess, I wonder
if you have some crufty client running that never reads input events
and does CopyArea or CopyPlane at a high rate without having disabled
graphics exposure events.  Perhaps you could state what clients you
typically run, and perhaps you could try a more controlled experiment
of leaving only "core" applications running overnight when xlock is
active.