Skip to content

gh-136421: Fix crash when _datetime is been initialized in multiple sub-interpreters #136422

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.

Sign up for GitHub

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+7 −1
Open

gh-136421: Fix crash when _datetime is been initialized in multiple sub-interpreters #136422

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f1e7225
Fix crash when _datetime is been initialized in multiple sub-interpre…
aisk Jul 8, 2025
b6735f6
Fix RST markers
aisk Jul 8, 2025
67cf8fd
Simplify the codes
aisk Jul 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions Misc/NEWS.d/next/Core_and_Builtins/2025-07-08-23-00-58.gh-issue-136421.uzieFA.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
Fix a crash when ``_datetime`` is being imported in multiple
sub-interpreters at the same time.
6 changes: 5 additions & 1 deletion Modules/_datetimemodule.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7344,9 +7344,13 @@ init_static_types(PyInterpreterState *interp, int reloading)

/* Bases classes must be initialized before subclasses,
* so capi_types must have the types in the appropriate order. */
static PyMutex mutex = {0};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the assumption is that this can run concurrently, then we need to also protect the assignments to tp_base above.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to clarify that I don't think this should be done with a mutex. An atomic global initialized variable should work and prevent double-initialization of the type.

for (size_t i = 0; i < Py_ARRAY_LENGTH(capi_types); i++) {
PyTypeObject *type = capi_types[i];
if (_PyStaticType_InitForExtension(interp, type) < 0) {
PyMutex_Lock(&mutex);
int ret = _PyStaticType_InitForExtension(interp, type);
PyMutex_Unlock(&mutex);
if (ret < 0) {
return -1;
}
}
Expand Down
Loading