Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!wsl.dec.com!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: X server supported Backing Store problems
Keywords: X backing-store
Message-ID: <1991Mar6.102313@wsl.dec.com>
Date: 6 Mar 91 18:23:13 GMT
References: <1991Mar4.171959.5134@applga.aa.cad.slb.com>
Sender: news@pa.dec.com (News)
Reply-To: klee@wsl.dec.com
Organization: DEC Western Software Laboratory
Lines: 24

In article <1991Mar4.171959.5134@applga.aa.cad.slb.com>, harper@applga.aa.cad.slb.com (Brett E. Harper) writes:
|>   The only problem is that sometimes the server simply stops maintaining the
|>   contents of my window (i.e. it STOPS doing backing store for me!) 
|>   When this happens the server starts sending me expose events for the 
|>   previously obscured regions (as the X manual says it will do) but I don't 
|>   want these, I want X to keep doing the backing store for me.  
|> 
|>   I am running on a HP9000s400 under HP-UX 7.03 using the Vue environment.  
|>   What I have noticed is that after time the size of the server (X) gets to
|>   be around 1100K big, then Pixmap allocations begin failing, and it seems that
|>   this is also around the time when the server stops doing backing store.
|>   The sure fire way to make backing store perform correctly is to kill the X   
|>   server and begin again (which makes the size of the server go down).

The X protocol allows servers to stop doing backing store whenever they
want.  Most will stop if memory becomes limited.  Sounds like you have
a memory leak in you server (do you mean 1100K or 11000K?), which would
cause memory problems.

-- 
Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee