-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
gh-88887: Cleanup multiprocessing.resource_tracker.ResourceTracker
upon deletion
#130429
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
Changes from 8 commits
069fb0c
5e33828
0586696
eeef2e4
b3115d2
cf3d546
933f70c
d4e08c5
799ee32
8e43a83
f9a53a7
805ad1d
5d6c9b3
c8e2704
9fd5872
aaa8378
dc2d578
9847342
58b137a
d497dee
ba42406
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1 @@ | ||||||
Fixing multiprocessing Resource Tracker process leaking | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is the issue specific to Python running as the pid 1? If yes, it might be useful to mention it in the Changelog entry. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the leaking happens regardless of PID 1. Python relies on kernel's process handling code to clean up the process, which works fine for most cases. A case where it won't work is when running Python as PID 1 and there's no signal processing handler to reap zombies on client code |
Uh oh!
There was an error while loading. Please reload this page.