-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
test_free_threading.test_racing_iter_extend
crash
#118561
Labels
tests
Tests in the Lib/test dir
topic-free-threading
type-bug
An unexpected behavior, bug, or error
type-crash
A hard crash of the interpreter, possibly with a core dump
Comments
colesbury
added
tests
Tests in the Lib/test dir
type-crash
A hard crash of the interpreter, possibly with a core dump
topic-free-threading
labels
May 3, 2024
I can reproduce this on The issue is that |
In particular the issue is the use of |
colesbury
added a commit
to colesbury/cpython
that referenced
this issue
May 7, 2024
The `list_preallocate_exact` function did not zero initialize array contents. In the free-threaded build, this could expose uninitialized memory to concurrent readers between the call to `list_preallocate_exact` and the filling of the array contents with items.
colesbury
added a commit
to colesbury/cpython
that referenced
this issue
May 7, 2024
The `list_preallocate_exact` function did not zero initialize array contents. In the free-threaded build, this could expose uninitialized memory to concurrent readers between the call to `list_preallocate_exact` and the filling of the array contents with items.
colesbury
added a commit
that referenced
this issue
May 9, 2024
…18723) The `list_preallocate_exact` function did not zero initialize array contents. In the free-threaded build, this could expose uninitialized memory to concurrent readers between the call to `list_preallocate_exact` and the filling of the array contents with items.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 9, 2024
…ld (pythonGH-118723) The `list_preallocate_exact` function did not zero initialize array contents. In the free-threaded build, this could expose uninitialized memory to concurrent readers between the call to `list_preallocate_exact` and the filling of the array contents with items. (cherry picked from commit 2402715) Co-authored-by: Sam Gross <colesbury@gmail.com>
colesbury
added a commit
that referenced
this issue
May 9, 2024
…ild (GH-118723) (#118863) The `list_preallocate_exact` function did not zero initialize array contents. In the free-threaded build, this could expose uninitialized memory to concurrent readers between the call to `list_preallocate_exact` and the filling of the array contents with items. (cherry picked from commit 2402715) Co-authored-by: Sam Gross <colesbury@gmail.com>
SonicField
pushed a commit
to SonicField/cpython
that referenced
this issue
May 10, 2024
…ld (python#118723) The `list_preallocate_exact` function did not zero initialize array contents. In the free-threaded build, this could expose uninitialized memory to concurrent readers between the call to `list_preallocate_exact` and the filling of the array contents with items.
@colesbury can we close this now? |
Yeah, I think so |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
tests
Tests in the Lib/test dir
topic-free-threading
type-bug
An unexpected behavior, bug, or error
type-crash
A hard crash of the interpreter, possibly with a core dump
Crash report
Seen in one of @swtaarrs's PRs:
https://github.com/python/cpython/actions/runs/8942881107/job/24566423243 (crash and then success)
Logs
cc @DinoV
Linked PRs
The text was updated successfully, but these errors were encountered: