Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: XSync(), XFlush(), and malloc()
Message-ID: <9008271313.AA08176@expire.lcs.mit.edu>
Date: 27 Aug 90 13:13:51 GMT
References: <MONTNARO.90Aug27085649@spyder.crd.ge.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 10


    Is there some kind soul who
    can explain where _XEnq()'s mallocated storage is freed, if at all?

Xlib maintains a global (not per display) free list of event queue elements.
They are never freed, not even at display close.  I guess the assumption is
that the free list would never get very large.  If you want to consider this
a bug, you are welcome to submit a bug report, but in that case please provide
a suggested effecient alternate implementation strategy, and explain why the
current implementation causes a real problem in your application.