-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Memleak tests #3140
Memleak tests #3140
Conversation
@alex, thanks for your PR! By analyzing the annotation information on this pull request, we identified @reaperhulk and @Ayrx to be potential reviewers |
The default malloc is CRYPTO_malloc which calls the custom ptr you provided, so it just recurses forever.
This reverts commit 37b9f3b.
So, very close. For some reason it fails on py35 and py26 on windows... and the tracebacks make no sense to me. @reaperhulk do you have opinions about how to dive in? really a pdb in there would go a long ways. |
Ok, figured out py26, it was warnings on stderr. I still have absolutely no clue about py35 |
Boom, tests are green now! |
Do we intend to run more substantial tests with the memory leak checks enabled in the future? |
@reaperhulk I plan to add specific memleak tests for known historical leaks. I don't see a practical way to run our existing tests with leak checking. |
They don't work, because something calls
OpenSSL_malloc
in the subprocess before we initialize it. I assume this comes from theBinding
init process