On Fri, Apr 29, 2016 at 02:08:06PM +0300, Pekka Paalanen wrote:
> On Fri, 29 Apr 2016 14:24:32 +0800
> Jonas Ådahl wrote:
>
> > On Thu, Apr 28, 2016 at 02:28:21PM +0300, Pekka Paalanen wrote:
> > > On Thu, 28 Apr 2016 15:31:31 +0800
> > > Jonas Ådahl wrote:
> > >
> > > > Using the libwayland-
On Fri, 29 Apr 2016 14:24:32 +0800
Jonas Ådahl wrote:
> On Thu, Apr 28, 2016 at 02:28:21PM +0300, Pekka Paalanen wrote:
> > On Thu, 28 Apr 2016 15:31:31 +0800
> > Jonas Ådahl wrote:
> >
> > > Using the libwayland-client client API with multiple threads with
> > > thread local queues are prone
On Thu, Apr 28, 2016 at 02:28:21PM +0300, Pekka Paalanen wrote:
> On Thu, 28 Apr 2016 15:31:31 +0800
> Jonas Ådahl wrote:
>
> > Using the libwayland-client client API with multiple threads with
> > thread local queues are prone to race conditions.
> >
> > The problem is that one thread can read
On 28/04/16 02:31 AM, Jonas Ådahl wrote:
> Using the libwayland-client client API with multiple threads with
> thread local queues are prone to race conditions.
>
> The problem is that one thread can read and queue events after another
> thread creates a proxy but before it sets the queue.
>
> Th
On Thu, 28 Apr 2016 15:31:31 +0800
Jonas Ådahl wrote:
> Using the libwayland-client client API with multiple threads with
> thread local queues are prone to race conditions.
>
> The problem is that one thread can read and queue events after another
> thread creates a proxy but before it sets the
Using the libwayland-client client API with multiple threads with
thread local queues are prone to race conditions.
The problem is that one thread can read and queue events after another
thread creates a proxy but before it sets the queue.
This may result in the event to the proxy being silently
