-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Use after free in 3.11 #96572
Comments
Hmm, this doesn't seem to reproduce all the time.. Might be flaky? |
@matthiasgoergens Thanks for the report. Please can you use git bisect to find when this started in Also ping release manager @pablogsal. |
Yes, I'll try bisecting. I'm not sure I have a 100% reliable way to trigger this, so I was suspicious of my previous bisection efforts. So I'm not even sure, whether it actually went away in main, or whether I just got (un)lucky recently. |
See also https://docs.python.org/3.11/whatsnew/changelog.html?highlight=_bootstrap_python#id77 and #90108 for some info on _bootstrap_python, which was re-introduced in 3.11. |
Hmm, whether I can trigger this problem seems to depend on the order in which Once I have a binary with the problem, I can trigger it reliably. But I can't reliably make a binary with the problem. |
Preliminarily: it looks like building |
I built main on MacOS 10.15.7 with Clang 12.0.0 with the same configure command and hit the same heap-use-after-free
I did some searching with lldb and it looks like the |
I am working on fix. |
See #96618 |
Should be fixed now. |
Awesome, thanks! |
@matthiasgoergens And thank you for both testing 3.11 and reporting! This got fixed just in time for 3.11 RC2 🚀 |
To be honest, I only tested 3.11, because I was trying to do a git bisect to figure out how and when the problem was introduced in main. :) |
When I try to build the current 3.11 0c81909 on my 64-bit ArchLinux machine with
clang version 14.0.6
and the following configuration:I get the following error:
This error also used to happen with
main
last week, but it seems not right now.The text was updated successfully, but these errors were encountered: