[Bug 2703] New: X resource leak in xcompmgr when using fades

[bugzilla-daemon at freedesktop.org]

Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=2703          
     
           Summary: X resource leak in xcompmgr when using fades
           Product: xorg
           Version: 6.8.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: App/other
        AssignedTo: xorg-bugzilla-noise at freedesktop.org
        ReportedBy: zlynx at acm.org


I noticed that after using xcompmgr with fades enabled for a long time I ran out
of memory.  I checked it out and discovered that not everything was being freed
when a window was destroyed.  Further checking discovered that an Unmap event
queues a fade which finishes the unmap after fading.  But immediately after the
Unmap event a disappearing window gets a Destroy event which queues a window
destroy event and deletes the queued unmap.  This results in the unmap never
running.

There's a "gone" parameter to the destroy functions which is checked to see if
it should run the unmap in the window destroy functions.  I don't understand
what "gone" is supposed to do but it seemed that the check to run unmap if !gone
in finish_destroy_window was backwards so I made it if (gone) instead, and
things seem to be working so far.          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.