<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - It's not safe to share wl_display fd with other threads."
href="https://bugs.freedesktop.org/show_bug.cgi?id=91273#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - It's not safe to share wl_display fd with other threads."
href="https://bugs.freedesktop.org/show_bug.cgi?id=91273">bug 91273</a>
from <span class="vcard"><a class="email" href="mailto:boram1288@gmail.com" title="Boram <boram1288@gmail.com>"> <span class="fn">Boram</span></a>
</span></b>
<pre><span class="quote">> I still don't understand what you mean by "the kernel may not wake up the
> thread" if it refers to a different issue than the two mentioned above.</span >
When A thread is polling on a display fd and B thread is polling on the same
display fd, if a server sends messages, sometimes only one thread(Let's say it
is B thread) awakes and reads all events so fast. Then A thread still is in the
polling status and can't awake. Even if B thread reads and queue all events
into corresponding queue_lists, the events of A thread's queue_list can't be
handled because A thread is still in sleep.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>