-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
BUG: fix use-after-free error in npy_hashtable.cpp #27955
Conversation
This fixes a universal segfault (on some platforms, others don't notice) on the free-threaded build on 2.2.0, so it would be nice to get an emergency 2.2.1 out with this applied. ping @charris sorry for the hassle! |
2.2.1 will happen pretty soon anyway, is it important enough to push out something before other fixes come in? (assuming they do) |
I'm not sure how annoying it is. We'll see if more reports come in on non-debug builds. |
I suppose sklearn, etc. might also have CI with this, let's see. |
BUG: fix use-after-free error in npy_hashtable.cpp (#27955)
In pandas we're also experiencing segfaults in our free threading, numpy 2.2 CI test build e.g. https://github.com/pandas-dev/pandas/actions/runs/12325213660/job/34404155884?pr=60562. The tests that were failing were calling I tried running the same build with the numpy nightly and it's passing now pandas-dev/pandas#60582, so I assume that this PR fixed our issues |
…0 segfaults (#60582) * Check if numpy/numpy#27955 fixes free-threading build * Add comments
Fixes #27953.
Those
Py_GIL_DISABLED
ifdefs clearly confused me.