Problem
My XSco process grows continuously and never seems to free memory.
Cause
The usual cause is allowing a client application such as Netscape
to continuously run. Netscape keeps asking the server to allocate
image space and then doesn't free it properly. This is actually a
memory leak on behalf of the X client transferred to the X server. It is therefore possible for an X server to appear to have a memory
leak. Earlier versions of the OpenServer X server did not have the
ability to recover their memory. Since OpenServer 5.0.4, the X server
will release its memory when the client that is hoarding it is shut
down, allowing the X server to release the freed memory. Thus, it can be a combination of X client and X server that causes
this problem. It depends upon how the X client behaves. Even well
behaved X clients can cause this problem if they do things like
allocating very large image spaces as well as small ones together.
A certain amount of memory fragmentation can occur over longer
periods of time which is impossible for the X server to coalesce
and recover. This is one reason why a desktop session logout will cause a
complete shutdown and restart of the X server, so it is not allowed
to run forever. Unfortunately some users never exit their desktop
session and they run clients like Netscape that are hard on the
memory allocator in the X server.And of course, there may be the case where a legitimate memory leak in the X server has been discovered.
Solution
The usual workaround is to have a periodic logout/shutdown of the
client application(s) and the desktop session to get the X server
restarted. The X server can usually recover if the Netscape is
periodically shutdown.If this does not free the memory resources, contact your Support provider.