It is known to everyone that locking serveral resources requires a consistent
order on all places where these resources are required. Otherwise a deadlock
src/video_out/video_out_vdpau.c | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
Am 15.07.2010 21:12, schrieb Reinhard Nissl:
> It is known to everyone that locking serveral resources requires a consistent
> order on all places where these resources are required. Otherwise a deadlock
> will happen.
I forgot to mention that Andreas Auras pointed this out. Thanks
again for the report.
Dipl.-Inform. (FH) Reinhard Nissl
Recently I've posted a patch for xine-ui which uses a timed lock to avoid a
deadlock when the output callback happens while changing the drawable. It is
possible to avoid this deadlock at all by moving the drawable lock (and the
reinit call which it is not necessary for the callback) after the callback.
As a result the mentioned patch for xine-ui may be reverted.
src/video_out/video_out_vdpau.c | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)