<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - memory leak of visual info" href="https://bugs.freedesktop.org/show_bug.cgi?id=64324#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - memory leak of visual info" href="https://bugs.freedesktop.org/show_bug.cgi?id=64324">bug 64324</a> from <a class="email" href="mailto:askinner@mathworks.com" title="Andy Skinner <askinner@mathworks.com>"> Andy Skinner</a> <pre>Any chance someone could look at this? We still get it reported as a leak, though it is in a large system and it would be hard to send a repro case. I admit we have't updated in a while, but the code is the same. If we could see this isn't a bug and we are using something wrong (our use of Mesa here is inside another 3rd party software library), that would also help. The difference between XMesaDestroyVisual (frees a single XMesaVisual and its XMesaVisualInfo) and destroy_visuals_on_display (only frees an array of XMesaVisuals but not their XMesaVisualInfos) seems clear. If destroy_visuals_on_display is not supposed to free the XVisualInfo, what is? The leaking object is said to be allocated in XGetVisualInfo, called from Fake_glXGetFBConfigs. Thanks.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>