Pycharm debugger instantly exits with 139 code

user_4601890 0
Viewed 18929

After upgrade from Pycharm 2017.2.3 to Pycharm 2017.1.4 Pycharm's Debugger suggested to build cpython (or sth associated with it):

path/to/my/python /opt/pycharm-community-2017.1.4/helpers/pydev/setup_cython.py build_ext --inplace

After I did this, Debugger now instantly returns this error:

Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

I found out that there was similar issue with cpython (https://youtrack.jetbrains.com/issue/PY-23273) but I cannot use the workaround mentioned there because I am missing the files it suggest to remove... I am not using cython, I wish I ignored this message about building it..

I am on linux (SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux)

Python 2.7

pycharm segmentation-fault upgrade
10 Answers

I've fixed it by disabling PyQt compatible option in PyCharms's debugger settings (Build, Execution, Deployment > Python Debugger). I don't use PyQt, so I have not met any troubles

user_37666830

Goto pycharm -> Preferences -> Build,Execution and deployment -> Python debugger

Check box Collect run-time types information for code insight.

This solved issues for me.

user_43944570

I had the same issue with 2018.3 after updating and installing Cython for fast debugging.

The issue was with gevent library.

Solved enabling Gevent compatible option and disabling PyQt compatible.

enter image description here

user_65954980

i meet this problem, and i search for it a long time, all caused by the compatible of pyqt,So I think a good idea to solve it....

  • uninstall pyqt and matplotlib
  • Fist install pyqt
  • Second install matplotlib

then the problem was solved happily.

user_73728020

Try clearing all your breakpoints. Worked for me. Also check you have no problem when doing Run instead of Debug.

user_6025430

I mostly randomly enabled and disabled Attach to subprocess automatically while debugging and PyQt compatible until I found a version that was stable for me. Eventually it was stable at Attach to subprocess automatically while debugging enabled and PyQt compatible enabled at auto.

I also followed 

 - uninstall pyqt and matplotlib
 - Fist install pyqt
 - Second install matplotlib
user_24393910

I had the same with 2017.1.4 Problem was resolved after update to 2017.1.5

user_25794990
Related