Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_multiprocessing segfaults on Windows #47374

Closed
theller opened this issue Jun 16, 2008 · 5 comments
Closed

test_multiprocessing segfaults on Windows #47374

theller opened this issue Jun 16, 2008 · 5 comments
Labels
type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@theller
Copy link

theller commented Jun 16, 2008

BPO 3124
Nosy @theller, @amauryfa

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2008-06-16.19:24:01.018>
created_at = <Date 2008-06-16.17:25:41.348>
labels = ['type-crash']
title = 'test_multiprocessing segfaults on Windows'
updated_at = <Date 2008-06-16.19:24:01.016>
user = 'https://github.com/theller'

bugs.python.org fields:

activity = <Date 2008-06-16.19:24:01.016>
actor = 'amaury.forgeotdarc'
assignee = 'none'
closed = True
closed_date = <Date 2008-06-16.19:24:01.018>
closer = 'amaury.forgeotdarc'
components = []
creation = <Date 2008-06-16.17:25:41.348>
creator = 'theller'
dependencies = []
files = []
hgrepos = []
issue_num = 3124
keywords = []
message_count = 5.0
messages = ['68274', '68275', '68277', '68288', '68291']
nosy_count = 3.0
nosy_names = ['theller', 'amaury.forgeotdarc', 'jnoller']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue3124'
versions = ['Python 2.6']

@theller
Copy link
Author

theller commented Jun 16, 2008

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
python26_d.dll!_Py_Dealloc(_object * op=0x012de740) Line 2043 + 0x9
bytes C
python26_d.dll!tupledealloc(PyTupleObject * op=0x00d58c78) Line 169 +
0x8a bytes C
python26_d.dll!_Py_Dealloc(_object * op=0x00d58c78) Line 2044 + 0x7
bytes C
python26_d.dll!PyObject_CallFunctionObjArgs(_object *
callable=0x00d64090, ...) Line 2716 + 0x51 bytes C
python26_d.dll!handle_callback(_PyWeakReference * ref=0x012de740,
_object * callback=0x00d64090) Line 864 + 0xf bytes C
python26_d.dll!PyObject_ClearWeakRefs(_object * object=0x012bcc98)
Line 910 + 0xd bytes C
python26_d.dll!func_dealloc(PyFunctionObject * op=0x012bcc98) Line
453 + 0x9 bytes C
python26_d.dll!_Py_Dealloc(_object * op=0x012bcc98) Line 2044 + 0x7
bytes C
python26_d.dll!tupledealloc(PyTupleObject * op=0x012ddeb8) Line 169 +
0x8a bytes C
python26_d.dll!_Py_Dealloc(_object * op=0x012ddeb8) Line 2044 + 0x7
bytes C
python26_d.dll!clear_slots(_typeobject * type=0x00cbbac8, _object *
self=0x012de740) Line 821 + 0x51 bytes C
python26_d.dll!subtype_dealloc(_object * self=0x012de740) Line 950
+ 0xd bytes C
python26_d.dll!_Py_Dealloc(_object * op=0x012de740) Line 2044 + 0x7
bytes C
python26_d.dll!dict_dealloc(_dictobject * mp=0x00d538c0) Line 907 +
0x6c bytes C
python26_d.dll!_Py_Dealloc(_object * op=0x00d538c0) Line 2044 + 0x7
bytes C
python26_d.dll!dict_dealloc(_dictobject * mp=0x00d536c8) Line 907 +
0x6c bytes C
python26_d.dll!_Py_Dealloc(_object * op=0x00d536c8) Line 2044 + 0x7
bytes C
python26_d.dll!instance_dealloc(PyInstanceObject * inst=0x00d60bf8)
Line 668 + 0x6c bytes C
python26_d.dll!_Py_Dealloc(_object * op=0x00d60bf8) Line 2044 + 0x7
bytes C
python26_d.dll!insertdict(_dictobject * mp=0x00d53620, _object *
key=0x00d5c9b8, long hash=-1896994012, _object * value=0x1e2bb004) Line
455 + 0x51 bytes C
python26_d.dll!PyDict_SetItem(_object * op=0x00d53620, _object *
key=0x00d5c9b8, _object * value=0x1e2bb004) Line 697 + 0x15 bytes C
python26_d.dll!_PyModule_Clear(_object * m=0x00d63968) Line 125 +
0x12 bytes C
python26_d.dll!PyImport_Cleanup() Line 479 + 0x9 bytes C
python26_d.dll!Py_Finalize() Line 452 C
python26_d.dll!Py_Exit(int sts=0) Line 1690 C
python26_d.dll!handle_system_exit() Line 1111 + 0x9 bytes C
python26_d.dll!PyErr_PrintEx(int set_sys_last_vars=1) Line 1123 C
python26_d.dll!PyErr_Print() Line 1030 + 0x7 bytes C
python26_d.dll!PyRun_SimpleFileExFlags(_iobuf * fp=0x10311448, const
char * filename=0x009d5d93, int closeit=1, PyCompilerFlags *
flags=0x0022ff30) Line 931 C
python26_d.dll!PyRun_AnyFileExFlags(_iobuf * fp=0x10311448, const char

  • filename=0x009d5d93, int closeit=1, PyCompilerFlags *
    flags=0x0022ff30) Line 731 + 0x15 bytes C
    python26_d.dll!Py_Main(int argc=5, char * * argv=0x009d5d68) Line 600
    + 0x39 bytes C
    python_d.exe!main(int argc=5, char * * argv=0x009d5d68) Line 23 +
    0xe bytes C
    python_d.exe!__tmainCRTStartup() Line 582 + 0x19 bytes C
    python_d.exe!mainCRTStartup() Line 399 C

@theller theller added the type-crash A hard crash of the interpreter, possibly with a core dump label Jun 16, 2008
@amauryfa
Copy link
Member

Can you check whether the patch for bpo-3100 corrects the problem?
(see PyObject_ClearWeakRefs in the call stack)

@theller
Copy link
Author

theller commented Jun 16, 2008

Yes, the patch weakref_cycle.patch from bpo-3100 fixes the problem.

@theller
Copy link
Author

theller commented Jun 16, 2008

Thomas Heller <theller@ctypes.org> added the comment:

Yes, the patch weakref_cycle.patch from bpo-3100 fixes the problem.

BTW: I also get a segfault on Linux, which is fixed by this patch.

@amauryfa
Copy link
Member

This is a duplicate of bpo-3100, which has been corrected by r64309.

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-crash A hard crash of the interpreter, possibly with a core dump
Projects
None yet
Development

No branches or pull requests

2 participants