<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - wayland: memory leak when exporting handle" href="https://bugzilla.gnome.org/show_bug.cgi?id=782109#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - wayland: memory leak when exporting handle" href="https://bugzilla.gnome.org/show_bug.cgi?id=782109">bug 782109</a> from <a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>Created <a href="attachment.cgi?id=351443&action=diff" name="attach_351443" title="GtkWindow: Don't double free export user data">attachment 351443</a> <a href="attachment.cgi?id=351443&action=edit" title="GtkWindow: Don't double free export user data">[details]</a> <a href='review?bug=782109&attachment=351443'>[review]</a> GtkWindow: Don't double free export user data The user data passed when exporting a Wayland window was supposed to be freed using the destroy_func, as is commonly done. This was previously broken, as the user data was just NULL:ed when exported, and only actually destroyed when unexporting before having exported. While e016d9a5dba6f6f99aee94d0b72c00bee299b96a fixed this, it introduced a regression, as GtkWindow was nice enough to free the memory anyway after having received the exported handle, causing it now to double free.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>