tom@ICASE.EDU (Tom Crockett) (02/01/90)
> *Excerpts from copies: 31-Jan-90 Re: X11R4 Xsun server appea.. => Bob* > *Scheifler@??? (2008)* > But I know at least one situation which causes the problem: running the old > R3 > xlock (compiled against R3) on the R4 server with "xset bc". After running > xlock overnight, I discovered that the server had grown by several megabytes. It also happens with the R4 xlock, I discovered. I'm using "xlock" off of the R4 contrib tape, plus the patches which Patrick Naughton posted on 12/19/89. After running "xlock" overnight with the previously posted arguments, I found that the server size (SZ) had grown from 940 to 6640. RSS grew a little, but stays reasonable. Tom Crockett ICASE Institute for Computer Applications in Science and Engineering M.S. 132C e-mail: tom@icase.edu NASA Langley Research Center phone: (804) 864-2182 Hampton, VA 23665-5225
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (02/02/90)
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.
rec@arris.com (Roger Critchlow) (02/02/90)
We're running X11R4, compiled with cc, on a SS-1. The server grew to 15 Mbytes between Sunday and Thursday. The primary client is a Symbolics UX400, but there are also instances of twm, xterm, and emacs active. The server is initiated by xdm, but logging out didn't change the server's memory size at all. Doesn't xdm send a SIGHUP to the server when the last client terminates? Isn't that supposed to reinitialize the server? -- rec --
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (02/03/90)
The primary client is a Symbolics UX400,
I've never looked at the Genera support, but it certainly wouldn't
surprise me to discover that it's client side allocates things and
never frees them (e.g. large pixmaps). There's no a priori reason
to blame the server.
Doesn't xdm send a SIGHUP to the server
when the last client terminates? Isn't that supposed to reinitialize
the server?
It does "reinitialize" the server, but that doesn't cause the process
size to shrink; you can only do that in a typical Unix by killing off
the process and starting a new one (e.g. by typing control-backslash at
the login prompt).