Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!jarthur!nntp-server.caltech.edu!ptimtc!rdmei!icspub!astemgw!wnoc-tyo-news!dclsic!sjc!leia!harkcom
From: harkcom@spinach.pa.yokogawa.co.jp
Newsgroups: comp.windows.x
Subject: freeing resources
Message-ID: <HARKCOM.91Feb27170212@spinach.pa.yokogawa.co.jp>
Date: 27 Feb 91 22:02:12 GMT
Sender: news@leia.pa.yokogawa.co.jp
Distribution: comp
Organization: Yokogawa Electric Corporation, Tokyo, Japan
Lines: 17

This may be a stupid question, but...

   Lately I have been wondering if there are any advantages to
freeing resources when you diconnect from the X server. I mean,
before I make a call to XCloseDisplay() I usually make calls
to XFreeThis and XFreeThat with a liberal dose of XDestroy all
around. I know that the server will do all of this for me in
most cases, but I've not bothered to figure out the difference.

   Are there any advantages in freeing and destroying or should
I just start calling XCloseDisplay() by itself and let the server
do the walking...?

   Are there cases where any memory allocated in the server for my
client will be left over?

   Will there be any nasty little Asynchronous errors popping up?