[issue35988] Python interpreter segfault

2019-02-14 Thread Hinko Kocevar
Hinko Kocevar added the comment: Thank you for the valuable information about the OOM beast.. -- ___ Python tracker <https://bugs.python.org/issue35988> ___ ___

[issue35988] Python interpreter segfault

2019-02-13 Thread Hinko Kocevar
Hinko Kocevar added the comment: Using python3.6 now. I've also used the 'handle SIGPIPE nostop noprint' to skip SIGPIPE. Now the interpreter is killed instead: INF 2019-02-13 15:42:19,131 web:2162 log_request - 200 GET /NPM.html (10.0.6.209) 1.10ms [Thread 0x7fffe76

[issue35988] Python interpreter segfault

2019-02-13 Thread Hinko Kocevar
Hinko Kocevar added the comment: > Are you able to reproduce the crash on Python 3.6 or 3.7? I'm running it under python3.6 as we speak. -- ___ Python tracker <https://bugs.python.org

[issue35988] Python interpreter segfault

2019-02-13 Thread Hinko Kocevar
New submission from Hinko Kocevar : I'm running a tornado server with websockets client. Every now and then the python3.5 crashes, seg faults. I added code tracking (https://stackoverflow.com/questions/2663841/python-tracing-a-segmentation-fault) and this is what I see: line, /usr/