Pycharm debugger instantly exits with 139 code

Question

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

Solution 1

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

Solution 2

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

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

This solved issues for me.

Solution 3

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.

Solution 4

I did change Pycharm from 2017.1.4 to Pycharm EAP 2017.2, but with no effect.

I solved the problem by making new python virtual environment and changing default Pycharm interpreter to it. Not the fastest solution I guess, but at least it worked.

Pycharm now again gives suggestions of building something for Cython, but now I just ignore it.

Solution 5

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.

View more solutions

Comments

[re-gor]

@Mike No, I don't, sorry. I've never worked with PyQt.

[YohanK]

I also faced the same issue after PyCharm got updated to 2018.3.1 (professional). The code I am testing could be debug previously but not after update. Uninstalling and reinstalling pyqt, matplotlib worked.

[Emrah Diril]

I have PySide2 installed, but not PyQt. Disabling PyQt compatible worked for me as well as setting it to PySide. However, setting it to PySide2 did not work even though that's what I have installed

[visoft]

The @re-gor solution worked once. I re-created my env and now I have no issues (at least few debugs)

[asad_hussain]

Worked for me. Thanks

[Erik]

I tried this while debugging PyTorch, but it didn't fix my problem

[Erik]

debugging pytorch, and this didn't fix the issue

[Erik]

this did not fix my problem debugging pytorch

[Hammurabi]

Thank you! That worked for me. In contrast, the other answers I tried (checking Gevent and unchecking PyQt) did not solve it for me.