[issue3124] test_multiprocessing segfaults on Windows

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: This is a duplicate of #3100, which has been corrected by r64309. -- resolution: -> duplicate status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue3124] test_multiprocessing segfaults on Windows

Thomas Heller <[EMAIL PROTECTED]> added the comment: > Thomas Heller <[EMAIL PROTECTED]> added the comment: > > Yes, the patch weakref_cycle.patch from #3100 fixes the problem. BTW: I also get a segfault on Linux, which is fixed by this patch. ___ Python tra

[issue3124] test_multiprocessing segfaults on Windows

Changes by Jesse Noller <[EMAIL PROTECTED]>: -- nosy: +jnoller ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing l

[issue3124] test_multiprocessing segfaults on Windows

Thomas Heller <[EMAIL PROTECTED]> added the comment: Yes, the patch weakref_cycle.patch from #3100 fixes the problem. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3124] test_multiprocessing segfaults on Windows

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Can you check whether the patch for issue3100 corrects the problem? (see PyObject_ClearWeakRefs in the call stack) -- nosy: +amaury.forgeotdarc ___ Python tracker <[EMAIL PROTECTED]>

[issue3124] test_multiprocessing segfaults on Windows

New submission from Thomas Heller <[EMAIL PROTECTED]>: When Python shuts down after running test_multiprocessing on Windows, a segfault occurs (this is with a debug build from trunk): > python26_d.dll!_Py_ForgetReference(_object * op=0x012de740) Line 2023 + 0xf bytes C python2