[issue17969] multiprocessing crash on exit
Kristján Valur Jónsson
report at bugs.python.org
Tue May 14 13:31:30 CEST 2013
Kristján Valur Jónsson added the comment:
Catching regressions is what we have the regression tests for. If it is not in caught by the regression tests, then it is not a regression, by definition.
Bug fix mode is for fixing bugs, IMHO.
Yes, I have patched my local version. The reason I am here having this discussion is that I want to contribute to help others that are using 2.7 for multiprocessing. Others will have the same problem, and probably have, already.
Anyway, I cannot easily reproduce the problem, it happens regularly in a live production environment. My patch is a conjecture based patch.
But I actually had a different thought about how to handle this.
The particular manifestation of this error occurs because an exception state is being cleared from the system dict. The dict contains a frame and there is where the connection object is being held.
The problem can be avoided, by clearing the exception right at the start of the PyInterpreterState_Clear(), thus flushing out most side effects right at the start.
I'll prepare a patch for you to review.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue17969>
_______________________________________
More information about the Python-bugs-list
mailing list