[Mesa-dev] [Bug 44151] New: glXDestroyWindow after glXDestroyContext -> Invalid read

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=44151

             Bug #: 44151
           Summary: glXDestroyWindow after glXDestroyContext -> Invalid
                    read
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: GLX
        AssignedTo: mesa-dev at lists.freedesktop.org
        ReportedBy: curaga at operamail.com


Created attachment 54822
  --> https://bugs.freedesktop.org/attachment.cgi?id=54822
Valgrind log

Mesa 7fd8dc3 / r600g

On exit from any Irrlicht-using app (1.7.2, any of the GL examples will do),
valgrind points out several invalid reads in r600_fence_reference.

The code in question is:
glXDestroyContext(display, Context);
if (glxWin)
        glXDestroyWindow(display, glxWin);

Which is a valid order, and also used in some of the mesa demos. Valgrind
doesn't complain on those though. While this may be something irrlicht is doing
wrong, there appears to be a check missing in Mesa that allows these invalid
reads.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.