This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay0410
Recipients damian.barabonkov, davin, gvanrossum, pablogsal, pitrou, vinay0410
Date 2020-08-06.18:24:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well, the chances of resource tracker dying abruptly are very less because it's thoroughly tested, and there are mechanisms to re-spawn resource_tracker process if you see the code. There is a function called `def ensure_running`.

Resource tracker is still alive even if the process for which it was created dies. It also handles cleaning shared semaphores. So, I guess this is something we can rely on for cleaning up things, because at the end of the day that's what it was made for.
Date User Action Args
2020-08-06 18:24:36vinay0410setrecipients: + vinay0410, gvanrossum, pitrou, davin, pablogsal, damian.barabonkov
2020-08-06 18:24:36vinay0410setmessageid: <>
2020-08-06 18:24:36vinay0410linkissue38119 messages
2020-08-06 18:24:36vinay0410create