From: Kacper Michajlow <kasper93@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v3] avformat/avisynth: fix segfault when also compiled with libvmaf Date: Mon, 28 Jul 2025 02:34:23 +0200 Message-ID: <CABPLASSn1yRJcwpbVtcZZxknvPcr43F8H4wsqoOZVjJkHGX52g@mail.gmail.com> (raw) In-Reply-To: <19ac6efe-69be-438e-a87b-ca9c91ab9290@gmail.com> On Mon, 28 Jul 2025 at 02:04, Daniel Bermond <danielbermond@gmail.com> wrote: > > When FFmpeg is compiled with support for both avisynth and libvmaf, > a segmentation fault occurs when using avisynth (.avs) input. > > This happens because both avisynthplus and vmaf have the exactly > same C++ symbol 'Cache::~Cache()'[1][2], which is a C++ destructor. > When using avisynth input, this destructor is also called in the > vmaf side, although no vmaf object was created, thus causing a > segmentation fault. > > Without changing this conflicting symbol in avisynthplus and/or > vmaf upstream code, a solution is to switch the 'RTLD_LOCAL'[3] I'm not opposed to a workaround to the issues as an interim solution, but has this issue been reported to upstream? Classes with such generic names should be put in a namespace in the respective projects. Additionally it would be good for those projects to be built with -fvisibility=hidden to reduce the amount of exposed symbols and only expose API entry points. - Kacper > flag for 'RTLD_DEEPBIND'[4] when calling 'dlopen()' on the > avisynthplus library. This will make the avisynthplus symbols > loaded by 'dlopen()' to be ahead of the symbols loaded in the > global scope, and consequently avoid the segmentation fault by > preventing the conflicting vmaf C++ destructor to be called. > > More details can be seen in the discussion of the Arch Linux bug > report[5] about this issue. > > [1] https://github.com/AviSynth/AviSynthPlus/blob/v3.7.5/avs_core/core/cache.h#L62 > [2] https://github.com/Netflix/vmaf/blob/v3.0.0/libvmaf/src/svm.cpp#L75 > [3] https://man.archlinux.org/man/dlopen.3#RTLD_LOCAL > [4] https://man.archlinux.org/man/dlopen.3#RTLD_DEEPBIND > [5] https://gitlab.archlinux.org/archlinux/packaging/packages/ffmpeg/-/issues/19 > > Signed-off-by: Daniel Bermond <danielbermond@gmail.com> > --- > libavformat/avisynth.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavformat/avisynth.c b/libavformat/avisynth.c > index cb2be10925..bef61b4a60 100644 > --- a/libavformat/avisynth.c > +++ b/libavformat/avisynth.c > @@ -120,7 +120,7 @@ typedef struct AviSynthContext { > > static av_cold int avisynth_load_library(AviSynthContext *avs) > { > - avs->avs_library.library = dlopen(AVISYNTH_LIB, RTLD_NOW | RTLD_LOCAL); > + avs->avs_library.library = dlopen(AVISYNTH_LIB, RTLD_NOW | RTLD_DEEPBIND); > if (!avs->avs_library.library) > return AVERROR_UNKNOWN; > > -- > 2.50.1 > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-28 0:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-28 0:04 Daniel Bermond 2025-07-28 0:34 ` Kacper Michajlow [this message] 2025-07-28 1:38 ` Stephen Hutchinson 2025-07-28 2:22 ` Stephen Hutchinson 2025-07-28 2:20 ` Daniel Bermond
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CABPLASSn1yRJcwpbVtcZZxknvPcr43F8H4wsqoOZVjJkHGX52g@mail.gmail.com \ --to=kasper93@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git