Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!bloom-beacon!dont-send-mail-to-path-lines
From: swick@athena.mit.EDU (Ralph Swick)
Newsgroups: comp.windows.x
Subject: Re: Quirky XtDestroyApplicationContext......???????
Message-ID: <9105301635.AA24558@lyre.MIT.EDU>
Date: 30 May 91 16:35:02 GMT
References: <1991May27.233521.8996@ptcburp.ptcbu.oz.au>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 15


     * Running this program generates the following message from within
     * XtCloseDisplay within XtDestroyApplication:-
     *
     * X Error of failed request:  BadAccess (attempt to access private resource denied)
     *   Major opcode of failed request:  88 (X_FreeColors)

Reproducing this is going to be very difficult without knowing
the contents of your resource files, but let me guess;

If you don't have R4 patched to fix #18 then some cases of StringToPixel
conversion (i.e. Alloc*Color) failures can cause this symptom.  (The
converter neglects to record the allocation failure and later on
cleanup from XtDestroyApplicationContext() it tries to free an
unallocated pixel.)