🚀 go-pugleaf

Please excuse any inappropriate cross-posting.

I noticed that each call to XCheckMaskEvent() causes some
memory to be allocated by a malloc() call, and NOT
subsequently freed before XCheckMaskEvent() returns.

I could observe this happening both under Linux (Xfree86)
and under Solaris 2.5.

This causes a memory leak to happen in applications that
call XCheckMaskEvent() very often, for example in a loop.


My questions are:

- Is it normal or is that a bug of XCheckMaskEvent() ?

- If this is normal, what is the application supposed to do to
free the memory that is allocated by XCheckMaskEvent() ?

- If it is a bug, is there a workaround ?

By the way, according to the manpage for XCheckMaskEvent(),
I don't see why XCheckMaskEvent() should allocate any memory
and not free it:


       Bool XCheckMaskEvent(display, event_mask, event_return)
             Display *display;
             long event_mask;
             XEvent *event_return;

       The XCheckMaskEvent function searches the event queue and
       then any events available on the server connection for the
       first event that matches the specified mask.  If it finds
       a match, XCheckMaskEvent removes that event, copies it
       into the specified XEvent structure, and returns True.
       The other events stored in the queue are not discarded.
       If the event you requested is not available, XCheck�
       MaskEvent returns False, and the output buffer will have
       been flushed.

Please help!

Regards, -- Tristan Savatier (mailto:tristan@mpegtv.com)
           
MpegTV website:   http://www.mpegtv.com
MPEG.ORG website: http://www.mpeg.org