On 7/19/24 12:56 PM, Stephen Hutchinson wrote:
The atexit() handler in the avisynth demuxer was added because
there was a conflict in AvxSynth that arose due to their use
of C++ global objects, particularly in relation to having
added a logging function relying on log4cpp.
This conflict was resp
On 7/28/24 11:59 AM, Stephen Hutchinson wrote:
On 7/28/24 9:38 AM, Ramiro Polla wrote:
@@ -1134,6 +1089,7 @@ static av_cold int
avisynth_read_close(AVFormatContext *s)
return AVERROR_UNKNOWN;
avisynth_context_destroy(s->priv_data);
+ dlclose(avs_library.library);
Maybe it'
On 7/28/24 9:38 AM, Ramiro Polla wrote:
@@ -1134,6 +1089,7 @@ static av_cold int avisynth_read_close(AVFormatContext *s)
return AVERROR_UNKNOWN;
avisynth_context_destroy(s->priv_data);
+dlclose(avs_library.library);
Maybe it's best to wrap this around an if (avs_library.lib
On Fri, Jul 19, 2024 at 7:51 PM Stephen Hutchinson wrote:
>
> The atexit() handler in the avisynth demuxer was added because
> there was a conflict in AvxSynth that arose due to their use
> of C++ global objects, particularly in relation to having
> added a logging function relying on log4cpp.
>
>
On 7/19/24 12:56 PM, Stephen Hutchinson wrote:
The atexit() handler in the avisynth demuxer was added because
there was a conflict in AvxSynth that arose due to their use
of C++ global objects, particularly in relation to having
added a logging function relying on log4cpp.
This conflict was resp
The atexit() handler in the avisynth demuxer was added because
there was a conflict in AvxSynth that arose due to their use
of C++ global objects, particularly in relation to having
added a logging function relying on log4cpp.
This conflict was responsible for causing a segfault on exit.
It did no
