Path: utzoo!utgpu!watserv1!watmath!att!rutgers!usc!sdd.hp.com!wuarchive!udel!haven!decuac!shlump.nac.dec.com!bacchus.pa.dec.com!wsl.dec.com!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: XAllocColor/XFreeColors question
Message-ID: <1990Oct19.104725@wsl.dec.com>
Date: 19 Oct 90 17:47:25 GMT
References: <31383@netnews.upenn.edu>
Sender: news@wrl.dec.com (News)
Reply-To: klee@wsl.dec.com
Distribution: na
Organization: DEC Western Software Laboratory
Lines: 25

In article <31383@netnews.upenn.edu>, bradley@grip.cis.upenn.edu (John Bradley) writes:
|> However, when I want to free the color cells, I have a bit of a problem.  On
|> certain MIT X11R4 servers, I've seen that color cells are not released unless
|> they are freed the same number of times that they were allocated, even if
|> the multiple allocations were all from one client.  This seems like perfectly
|> reasonable behavior, and I can live with it.
|> 
|> Unfortunately, OTHER X servers (IBM 6000/AIX 3.1, and others) get all bent-
|> out-of-shape if I try to free the same color cell more than once.

This sentence appears in the X11R4 protocol spec:

"A read-only entry is not actually freed until it has been freed by all
clients, and if a client allocates the same read-only entry multiple
times, it must free the entry that many times before the entry is
actually freed."

The sentence did not appear in the X11R3 spec, so older servers may
behave differently.

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