[issue3100] segfault from multiprocessing.util.register_after_fork

Changes by Adam Olsen <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10610/register_after_fork-crash.py ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3100] segfault from multiprocessing.util.register_after_fork

Changes by Adam Olsen <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10612/inner.py ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3100] segfault from multiprocessing.util.register_after_fork

Adam Olsen <[EMAIL PROTECTED]> added the comment: Very specific test case, eliminating multiprocessing entirely. It may be an interaction between having the watched obj as its own key in the WeakValueDictionary and the order in which the two modules are cleared. Added file: http://bugs.python.o

[issue3100] segfault from multiprocessing.util.register_after_fork

Adam Olsen <[EMAIL PROTECTED]> added the comment: More specific test case. -- title: segfault after loading multiprocessing.reduction -> segfault from multiprocessing.util.register_after_fork Added file: http://bugs.python.org/file10610/register_after_fork-crash.py