Prevent early destruction of gFuns, fixes AddressSanitizer: heap-use-after-free #22386
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 now fully understand what is happening in #22082.
The real cause of the problem is that the destruction of global var gFuns in lib/std/exitprocs.nim is too early before the atexit call to callClosures.
With a few lines of code, I can now reproduce this problem in a stable way.
After this patch, AddressSanitizer: heap-use-after-free no longer exists. this fixes the problem for both 1.6.x and 2.0.0.