-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
Python array
module is not free-thread safe.
#128942
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
Comments
Thanks! |
…)" The change regressed performance on scimark benchmarks from the pyperformance benchmark suite. This reverts commit 8ba0d7b.
Re-opening due to performance regression on pyperformance. Let's try to benchmark future PRs that may be performance sensitive. I usually use https://github.com/colesbury/fastbench because it's quick to run and well correlated with the full pyperformance run. There's also the runners for pyperformance at: https://github.com/facebookexperimental/free-threading-benchmarking |
Co-authored-by: Kumar Aditya <kumaraditya@python.org>
…)" (python#130707) The change regressed performance on scimark benchmarks from the pyperformance benchmark suite. This reverts commit 8ba0d7b.
Bug report
Bug description:
The python
array
module is not currently free-thread safe. The error generator below can generate segfaults of aborts for most of thearray
object methods. I found #116738 which lists this module as in need of an audit, an apparenly closed start on this in #120103 and no owner for this module in the Experts Index, so decided to give it a go (see attached PR).Reproducer, any single
check(...)
call below will generate some kind of segfault or abort fairly quickly.CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Linked PRs
array
module thread safe (#128943)" #130707The text was updated successfully, but these errors were encountered: