-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Crash for 3.13rc1 on Windows with free threading during initialize #122918
Comments
This is compiled from source against the 3.13rc1 tag |
We saw these sorts of crashes before when the free-threaded interpreter was loading shared libraries compiled for the default build. Does the crash go away if you do a "clean" build? |
I tried A fresh clone worked against main and the v3.13.0rc1 tags. We can either close this or improve |
Improving the |
Adding a |
I'm seeing similar crashes in my PyO3 dev environment on MacOS. Interestingly, it doesn't happen if I use a debug python 3.13 free-threaded build. May be completely unrelated to the Windows-specific issues described above. Here's the traceback from the crash:
Both the debug python build and the optimized, crashing Python are built from source using pyenv. |
That looks unrelated to the Windows issues. The traceback makes me thing there is a bug in CPython (not just PyO3). Opened a new issue: #123022 |
Crash report
What happened?
I'm trying to use Python 3.13rc1 with free-threading and debugging enabled on Windows 11. On startup, Python crashes. I've got a stack trace of the issue, which is pointing to the ob_type being invalid for an object during the startup sequence.
When I run Python at the command line (for anything other than show version) it crashes immediately.
Full stack trace
CPython versions tested on:
CPython main branch
Operating systems tested on:
Windows
Output from running 'python -VV' on the command line:
Python 3.13.0rc1 experimental free-threading build (tags/v3.13.0rc1:e4a3e786a5e, Aug 12 2024, 08:07:19) [MSC v.1940 64 bit (AMD64)]
The text was updated successfully, but these errors were encountered: