Skip to content

bpo-36533: Reinit logging.Handler locks on fork(). #12704

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

Merged
merged 1 commit into from
May 7, 2019

Conversation

gpshead
Copy link
Member

@gpshead gpshead commented Apr 6, 2019

Instead of attempting to acquire and release them all across fork
which was leading to deadlocks in some applications that had chained
their own handlers while holding multiple locks.

https://bugs.python.org/issue36533

Instead of attempting to acquire and release them all across fork
which was leading to deadlocks in some applications that had chained
their own handlers while holding multiple locks.
@gpshead
Copy link
Member Author

gpshead commented Apr 6, 2019

Do not merge label applied while deciding which way forward we want to go. This is one option.

@miss-islington
Copy link
Contributor

Thanks @gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖

@gpshead gpshead deleted the logging_lock_36533 branch May 7, 2019 16:18
@gpshead gpshead added sprint type-bug An unexpected behavior, bug, or error labels May 7, 2019
gpshead added a commit to gpshead/cpython that referenced this pull request May 7, 2019
)

Instead of attempting to acquire and release them all across fork
which was leading to deadlocks in some applications that had chained
their own handlers while holding multiple locks.
(cherry picked from commit 64aa6d2)

Co-authored-by: Gregory P. Smith <[email protected]>
@bedevere-bot
Copy link

GH-13170 is a backport of this pull request to the 3.7 branch.

gpshead added a commit that referenced this pull request May 7, 2019
…H-13170)

Instead of attempting to acquire and release them all across fork
which was leading to deadlocks in some applications that had chained
their own handlers while holding multiple locks.
(cherry picked from commit 64aa6d2)

Co-authored-by: Gregory P. Smith <[email protected]>  [Google LLC]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sprint type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants