[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

Hirokazu Yamamoto added the comment: This seems to be duplicate of issue1856. Let me close this entry. -- resolution: -> duplicate status: open -> closed superseder: -> shutdown (exit) can hang or segfault with daemon threads running ___ Python tra

[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

Corey Goldberg added the comment: note: on Windows Vista it is not ery intermittant :) crashes every time the program is stopped. ___ Python tracker ___ __

[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

Hirokazu Yamamoto added the comment: Here is stack trace. PyEval_EvalFrameEx(_frame * 0x00a62060, int 83) line 2841 + 6 bytes fast_function(_object * 0x, _object * * * 0x00fbfa98, int 1, int 1, int 9870576) line 3946 call_function(_object * * * 0x00fbfa98, int 0) line 3880 + 16 bytes Py

[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

Corey Goldberg added the comment: little more info: If you create a Queue in the main thread and pass this to each worker thread, it works fine. If you create the Queue inside the worker thread and then pass it to a new thread, it can crash. when it crashes, you get an immediate core dump wi

[issue5160] Intermittant segmentation fault with ctrl-c (threads and queues)

New submission from Corey Goldberg : I can get the Python interpreter to core dump when running the following code: http://pastebin.com/f261f398f To reproduce: - run the above code and press ctrl-c to quit while it is running. It crashes (segfault) the interpreter every few times you stop it l