[Wayland-bugs] [Bug 87824] Dangling pointers and memory corruption after output recreate.

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Andriy Prystupa <andriy.prystupa at globallogic.com> ---
>> 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20150105/0216ee19/attachment.html>