From: Stephen Hutchinson <qyot27@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] libavformat/vapoursynth: Update to API version 4, load library at runtime
Date: Fri, 19 Jul 2024 13:05:10 -0400
Message-ID: <433c95ea-8982-4818-bdb8-82135a0d814e@gmail.com> (raw)
In-Reply-To: <27c8d4df-7dc0-4f15-8590-42c6b016c2bb@gmx.net>
On 7/18/24 10:53 AM, Stefan Oltmanns via ffmpeg-devel wrote:
> The AviSynth patch to remove it by Stephen Hutchinson does not introduce
> it somewhere else. It is now only called directly at the start in case a
> needed function cannot be loaded from the DLL.
> From what I read dlclose is only needed if there are any C++
> deconstructors or similar stuff that need to be called before exiting
> the program.
> dlclose usually won't unload the library anyway (the spec does not
> require dlclose to do that)
>
That was just an oversight. Interestingly, the only situation that
the lack of dlclose appeared to cause a problem with when testing was
when the AviSynth host was the standard MSVC build for IA32, under
which case the lack of dlclose caused a segfault on exit. The 64-bit
build was fine and so were amd64 and i686 GCC builds.
Odd, but regardless, fixed in the newer version of the patch.
_______________________________________________
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:[~2024-07-19 17:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 21:08 Stefan Oltmanns via ffmpeg-devel
2024-07-18 9:37 ` Stefan Oltmanns via ffmpeg-devel
2024-07-18 11:25 ` Anton Khirnov
2024-07-18 15:38 ` Stefan Oltmanns via ffmpeg-devel
2024-07-22 6:57 ` Anton Khirnov
2024-07-23 0:24 ` Stefan Oltmanns via ffmpeg-devel
2024-07-18 11:08 ` Ramiro Polla
2024-07-18 12:48 ` Stefan Oltmanns via ffmpeg-devel
2024-07-18 13:04 ` Ramiro Polla
2024-07-18 13:41 ` Stefan Oltmanns via ffmpeg-devel
2024-07-18 14:21 ` Ramiro Polla
2024-07-18 14:53 ` Stefan Oltmanns via ffmpeg-devel
2024-07-19 17:05 ` Stephen Hutchinson [this message]
2024-07-18 15:23 ` epirat07
2024-07-21 22:08 ` Stefan Oltmanns via ffmpeg-devel
2024-07-21 22:15 ` Hendrik Leppkes
2024-07-22 0:42 ` Stefan Oltmanns via ffmpeg-devel
2024-07-22 6:36 ` Hendrik Leppkes
2024-07-22 12:13 ` Ramiro Polla
2024-07-22 13:41 ` Hendrik Leppkes
2024-07-22 18:28 ` Ramiro Polla
2024-07-22 13:52 ` Stefan Oltmanns via ffmpeg-devel
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=433c95ea-8982-4818-bdb8-82135a0d814e@gmail.com \
--to=qyot27@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