This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients christian.heimes, methane, ned.deily, python-dev, serhiy.storchaka, vstinner, yselivanov
Date 2016-10-18.21:20:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476825614.93.0.254314012726.issue28471@psf.upfronthosting.co.za>
In-reply-to
Content
I'm curious. I tested in release mode, the example does crash:

$ ./python x.py 
Segmentation fault (core dumped)


I'm able to get a Python traceback using PYTHONMALLOC=debug:

$ PYTHONMALLOC=debug ./python x.py 
Fatal Python error: Python memory allocator called without holding the GIL

Current thread 0x00007f65bd74b700 (most recent call first):
  File "/home/haypo/prog/python/default/Lib/asyncio/base_events.py", line 790 in _create_connection_transport
  File "/home/haypo/prog/python/default/Lib/asyncio/base_events.py", line 777 in create_connection
  File "/home/haypo/prog/python/default/Lib/asyncio/streams.py", line 75 in open_connection
  File "x.py", line 13 in client
  File "x.py", line 16 in runner
  File "/home/haypo/prog/python/default/Lib/asyncio/tasks.py", line 239 in _step
  File "/home/haypo/prog/python/default/Lib/asyncio/events.py", line 126 in _run
  File "/home/haypo/prog/python/default/Lib/asyncio/base_events.py", line 1390 in _run_once
  File "/home/haypo/prog/python/default/Lib/asyncio/base_events.py", line 405 in run_forever
  File "/home/haypo/prog/python/default/Lib/asyncio/base_events.py", line 437 in run_until_complete
  File "x.py", line 18 in <module>
Aborted (core dumped)
History
Date User Action Args
2016-10-18 21:20:15vstinnersetrecipients: + vstinner, christian.heimes, ned.deily, methane, python-dev, serhiy.storchaka, yselivanov
2016-10-18 21:20:14vstinnersetmessageid: <1476825614.93.0.254314012726.issue28471@psf.upfronthosting.co.za>
2016-10-18 21:20:14vstinnerlinkissue28471 messages
2016-10-18 21:20:14vstinnercreate