On Sat, 25 Mar 2017 13:25:32 +0100
Michael Niedermayer wrote:
> On Sat, Mar 25, 2017 at 01:13:13PM +0100, wm4 wrote:
> > On Sat, 25 Mar 2017 13:01:58 +0100
> > Michael Niedermayer wrote:
> >
> > > On Sat, Mar 25, 2017 at 12:03:23PM +0100, wm4 wrote:
> > > > On Fri, 24 Mar 2017 18:53:41 +010
On Sat, Mar 25, 2017 at 01:13:13PM +0100, wm4 wrote:
> On Sat, 25 Mar 2017 13:01:58 +0100
> Michael Niedermayer wrote:
>
> > On Sat, Mar 25, 2017 at 12:03:23PM +0100, wm4 wrote:
> > > On Fri, 24 Mar 2017 18:53:41 +0100
> > > Michael Niedermayer wrote:
> > >
> > > > On Fri, Mar 24, 2017 at 01:
On Sat, 25 Mar 2017 13:01:58 +0100
Michael Niedermayer wrote:
> On Sat, Mar 25, 2017 at 12:03:23PM +0100, wm4 wrote:
> > On Fri, 24 Mar 2017 18:53:41 +0100
> > Michael Niedermayer wrote:
> >
> > > On Fri, Mar 24, 2017 at 01:47:10PM +0100, wm4 wrote:
> > > > async_mutex has is used in a very
On Sat, Mar 25, 2017 at 12:03:23PM +0100, wm4 wrote:
> On Fri, 24 Mar 2017 18:53:41 +0100
> Michael Niedermayer wrote:
>
> > On Fri, Mar 24, 2017 at 01:47:10PM +0100, wm4 wrote:
> > > async_mutex has is used in a very strange but intentional way: it is
> > > locked by default, and unlocked only i
On Fri, 24 Mar 2017 18:53:41 +0100
Michael Niedermayer wrote:
> On Fri, Mar 24, 2017 at 01:47:10PM +0100, wm4 wrote:
> > async_mutex has is used in a very strange but intentional way: it is
> > locked by default, and unlocked only in regions that can be run
> > concurrently.
> >
> > If the user
On Fri, 24 Mar 2017 18:53:41 +0100
Michael Niedermayer wrote:
> On Fri, Mar 24, 2017 at 01:47:10PM +0100, wm4 wrote:
> > async_mutex has is used in a very strange but intentional way: it is
> > locked by default, and unlocked only in regions that can be run
> > concurrently.
> >
> > If the user
On Fri, Mar 24, 2017 at 01:47:10PM +0100, wm4 wrote:
> async_mutex has is used in a very strange but intentional way: it is
> locked by default, and unlocked only in regions that can be run
> concurrently.
>
> If the user was calling API functions to the same context from different
> threads (in a
async_mutex has is used in a very strange but intentional way: it is
locked by default, and unlocked only in regions that can be run
concurrently.
If the user was calling API functions to the same context from different
threads (in a safe way), this could unintentionally unlock the mutex on
a diff