Fix TLS segfault in windows static build. #222
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed a segfault when using avs+ windows static build, which I managed to reproduce with this simple sample program:
I traced the segfault to this location in the code:
https://github.com/AviSynth/AviSynthPlus/blob/master/avs_core/core/avisynth.cpp#L2224
The
dwTlsIndex
variable is set during DllMain:https://github.com/AviSynth/AviSynthPlus/blob/master/avs_core/core/main.cpp#L285
which is obviously not called when the static library is built. The patch moves TlsAlloc/TlsFree to the constructor/destructor of a statically initialized object instead. A simpler solution might be to simply drop XP support and rely on
__declspec(thread)
instead, but I guess that might be more contentious.