[rtmpdump] librtmp thread-safeness question

Andrey Turkin andrey.turkin at gmail.com
Thu Dec 18 09:09:48 CET 2014

2014-12-17 11:25 GMT+03:00 Rafaël Carré <funman at videolan.org>:

> Check this patch:
> https://lists.mplayerhq.hu/pipermail/rtmpdump/2014-September/002380.html

Thanks for the answer (though this patch cannot help me because I'm using
Zeranoe builds of libav libraries and cannot patch anything). I found how
to "trick" librtmp into initializing itself via libav API so this issue
isn't pressing for me anymore. However this bug remains, with at least
Zeranoe builds (and probably many others) affected and it should be fixed
in tree.
So my question remains. I hope someone maintaining librtmp is reading this
list and can give some answer. Basically, either of "it is librtmp's bug
and we won't fix it", "it is librtmp's bug and we are going to fix it", "it
is not librtmp's bug because ffmpeg/libav is using it wrong in such and
such ways" (in which case I'll go bug ffmpeg people) or "these API
functions are not thread-safe and these are with following conditions" will

  Andrey Turkin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mplayerhq.hu/pipermail/rtmpdump/attachments/20141218/fb04d4d6/attachment.html>

More information about the rtmpdump mailing list