<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Dangling pointers and memory corruption after output recreate." href="https://bugs.freedesktop.org/show_bug.cgi?id=87824#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Dangling pointers and memory corruption after output recreate." href="https://bugs.freedesktop.org/show_bug.cgi?id=87824">bug 87824</a> from <a class="email" href="mailto:andriy.prystupa@globallogic.com" title="Andriy Prystupa <andriy.prystupa@globallogic.com>"> Andriy Prystupa</a> <pre>>> So, is this bug about some shell plugin not doing its job, needing the safety >> measure, or removing the last output leaving no outputs at all? My case is leaving no outputs at all for a while. Exact scenario: - got event from HW - in event handler destroy output and immediately create new one. I am not sure if shell plugin will get control between destroy and create. And situation gets worth because of undetermined behavior of heap manager: when we do free(output) and then immediately alloc() pointer value lefts the same(at least in my case). Its hard to prognose possible bugs. To my mind it might be more stable if weston compositor will throw off incorrect pointers and unmap view(or mark it as to be remmaped) on destroy output.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>