[issue43145] Leak of locks from multiprocessing.Process

hai shi added the comment: > The following locks are leaked: > 1. > https://github.com/python/cpython/blob/196d4deaf4810a0bba75ba537dd40f2d71a5a634/Python/pystate.c#L78 > 2. > https://github.com/python/cpython/blob/196d4deaf4810a0bba75ba537dd40f2d71a5a634/Python/pystate.c#L84 > 3. >

[issue43145] Leak of locks from multiprocessing.Process

Change by Terry J. Reedy : -- nosy: +davin, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43145] Leak of locks from multiprocessing.Process

Boris Staletic added the comment: The `multiprocessing.Process`, on Linux, ends up doing something like this: pid = os.fork() if pid == 0: os._exit() Translated to C: int main() { Py_Initialize(); PyOS_BeforeFork(); pid_t pid = fork(); if (pid == 0) {

[issue43145] Leak of locks from multiprocessing.Process

Change by Gregory P. Smith : -- title: Leak of locks in a subprocess -> Leak of locks from multiprocessing.Process ___ Python tracker ___