Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!think.com!paperboy!osf.org!dbrooks
From: dbrooks@osf.org (David Brooks)
Newsgroups: comp.windows.x
Subject: Re:  resource ID allocation
Message-ID: <18984@paperboy.OSF.ORG>
Date: 14 Feb 91 14:27:39 GMT
References: <9102140823.AA17984@lightning.McRCIM.McGill.EDU>
Sender: news@OSF.ORG
Reply-To: dbrooks@osf.org (David Brooks)
Organization: Open Software Foundation
Lines: 24

In article <9102140823.AA17984@lightning.McRCIM.McGill.EDU>, mouse@lightning.mcrcim.mcgill.EDU writes:
|> This seems like a silly thing to worry about.  However, suppose someone
|> has some program running for weeks, creating and destroying windows,
|> GCs, whatever, and then as it gets old, it crashes when its Xlib
|> creates an invalid XID...unless Xlib does get this right, of course!
|> (I haven't checked the source.)

Actually, this happened to a customer of ours, but the other way
round.  They had a long-running client that did a lot of repetitive
mapping/unmapping windows, which eventually translated into a sequence
of grab/ungrab (Ihope I'm getting the details right).  The server
allcoated a new Server-private XID for each, and eventually overflowed
its private bit into the client space.  On the next free, it freed
some random XID, much to the client's surprise, and all hell broke
lose (well, it didn't actually; usually it froze).

That took some debugging, especially as it takes hours to make it
happen each time...

The customer redesigned the application, I think.
-- 
David Brooks				dbrooks@osf.org
Systems Engineering, OSF		uunet!osf.org!dbrooks
"Home is the bright cave under the hat." -- Lance Morrow