🚀 go-pugleaf

> This simple program leaks like hell... We strongly suspect the
> XtAppAddWorkProc which is done in the TimeOut function.

In most R4 Xt libraries, returning True from a work procedure will cause
a memory leak.  To work around the bug, the work procedure can be removed
from the queue of work procedures by calling XtRemoveWorkProc, which will
not leak; however please note that it is unacceptable practice to make
this call from the same work procedure which is being removed.  


> Is there any fix for this leak. (I have not tried in X11R5)

This bug is not present in the R5 Xt library. 
And sure, there's a fix, and if you have the source you can fix it
yourself.  Make the following change (the single line marked by
an exclaimation point; buggy code appears first, correct code
appears second) to the code in CallWorkProc in the file NextEvent.c.

  
        if (delete) {
            w->next = freeWorkRecs;
!           freeWorkRecs = w->next;
        }
        else {
            w->next = app->workQueue;
--- ---
  
        if (delete) {
            w->next = freeWorkRecs;
!           freeWorkRecs = w;
        }
        else {
            w->next = app->workQueue;



Donna Converse
MIT X Consortium