Issue 19650: test_multiprocessing_spawn.test_mymanager_context() crashed with STATUS_ACCESS_VIOLATION (original) (raw)

Issue19650

Created on 2013-11-19 09:53 by vstinner, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg203346 - (view)	Author: STINNER Victor (vstinner) *	Date: 2013-11-19 09:53
The following failure may be related to #19466. I failed to reproduce it on my Windows 7 VM (I compiled Python in 32-bit mode). http://buildbot.python.org/all/builders/x86%20Windows%20Server%202008%20%5BSB%5D%203.x/builds/1697/steps/test/logs/stdio ====================================================================== FAIL: test_mymanager_context (test.test_multiprocessing_spawn.WithManagerTestMyManager) ---------------------------------------------------------------------- Traceback (most recent call last): File "E:\home\cpython\buildslave\x86\3.x.snakebite-win2k8r2sp1-x86\build\lib\test\_test_multiprocessing.py", line 1960, in test_mymanager_context self.assertEqual(manager._process.exitcode, 0) AssertionError: 3221225477 != 0 3221225477 is 0xC0000005 in hex, Windows error code: #define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC0000005L)
msg222654 - (view)	Author: Mark Lawrence (BreamoreBoy) *	Date: 2014-07-10 08:55
Can this be reproduced or can this be closed as out of date?
msg222655 - (view)	Author: STINNER Victor (vstinner) *	Date: 2014-07-10 08:58
> Can this be reproduced or can this be closed as out of date? In general, issues reporting sporadic buildbot failures only seen once can be closed after 6 months.