diff options
| author | wm4 <wm4@nowhere> | 2019-09-20 16:43:17 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2019-09-20 16:47:16 +0200 |
| commit | 4fa8f33b92a44fe928817a81653f135402192cac (patch) | |
| tree | fb4cd74997b4b6fb79116d9798574a32f0071037 /libmpv | |
| parent | f00af71d12a7d155d4d80f0879931c3f54c7ab9b (diff) | |
| download | mpv-4fa8f33b92a44fe928817a81653f135402192cac.tar.bz2 mpv-4fa8f33b92a44fe928817a81653f135402192cac.tar.xz | |
client API, vo_libmpv: document random deadlock problems
I guess trying to make DR work on libmpv was a mistake.
I never observed such a deadlock, but it's looks like it's theoretically
possible.
Diffstat (limited to 'libmpv')
| -rw-r--r-- | libmpv/render.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/libmpv/render.h b/libmpv/render.h index 086b42d1b5..6d594e0c06 100644 --- a/libmpv/render.h +++ b/libmpv/render.h @@ -85,6 +85,10 @@ extern "C" { * requirement always existed. Not honoring it will lead to UB (deadlocks, * use of invalid pthread_t handles). This requirement might be removed in * the future, but will require some considerable work internal to libmpv. + * You can avoid this issue by setting "vd-lavc-dr" to "no". + * - MPV_RENDER_PARAM_ADVANCED_CONTROL has some other libmpv-internal problems, + * which may result in random deadlocks (see top of vo_libmpv.c). + * You can probably avoid this issue by setting "vd-lavc-dr" to "no". * * libmpv functions which are safe to call from a render thread are: * - functions marked with "Safe to be called from mpv render API threads." |