-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Valgrind reports memory leak in flisp #13540
Comments
I think you're right that this is probably just due to not running finalizers on exit. |
JeffBezanson
added
the
status:won't change
Indicates that work won't continue on an issue or pull request
label
Oct 21, 2015
Can we add a sanitizer/valgrind only codepath that calls the finalizers on exit? |
If someone is going to go to the effort of writing the code to call finalizers on exit, why wouldn't you run it unconditionally? |
Keno
removed
the
status:won't change
Indicates that work won't continue on an issue or pull request
label
Aug 11, 2022
Closed by #46249 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I assume this may just be because flisp doesn't run finalizers in deinitialization, but just in case and for posterity, valgrind reports the following (found because address sanitizer complains as well):
The text was updated successfully, but these errors were encountered: