Andreas Rheinhardt (12021-08-11): > Both the name as well as the options need to be freed. > (Right now there is no option for the AVFilterContext itself that could > leak, but some filters have options (e.g. of type AV_OPT_TYPE_STRING) > that can leak.) > > Signed-off-by: Andreas Rheinhardt <andreas.rheinha...@outlook.com>
LGTM. > I intend to remove this duplicated freeing code and call avfilter_free() > directly once it is ensured that it is safe to do so; a few checks will > have to be added to it and the filters will have to be checked to be > compatible with it. The only thing I already found out is that libvamf > is buggy (even without calling avfilter_free), because it just presumes > that a mutex and a condition variable have always been properly > initialized. Useful work, thanks. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
