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

This seems to happen regardless of python version. I get it when trying to debug code on a remote machine, in Pycharm Pro version; the interpreter I used was python3.5, from anaconda environment. Disabling PyQt (see re-gor's answer) solved the problem. — Mircea, Jul 13 '18 at 08:52

score 63 · Accepted Answer · answered Oct 22 '17 at 20:27

63

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

answered Oct 22 '17 at 20:27

re-gor

1,311
11
17

@Mike No, I don't, sorry. I've never worked with PyQt. – re-gor Jul 26 '18 at 07:05
1

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 – Emrah Diril Aug 14 '19 at 06:13
Worked for me. Thanks – asad_hussain Jan 24 '20 at 07:19
I tried this while debugging PyTorch, but it didn't fix my problem – Erik Jun 09 '21 at 21:15

score 31 · Answer 2 · answered Aug 27 '20 at 17:47

31

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

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

This solved issues for me.

answered Aug 27 '20 at 17:47

Sanchit

347
4
10

1

this did not fix my problem debugging pytorch – Erik Jun 09 '21 at 21:16
5

Thank you! That worked for me. In contrast, the other answers I tried (checking Gevent and unchecking PyQt) did not solve it for me. – Hammurabi Dec 08 '21 at 00:15

score 10 · Answer 3 · answered Feb 26 '19 at 14:30

10

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.

answered Feb 26 '19 at 14:30

Marcos Martínez

545
2
9
24

debugging pytorch, and this didn't fix the issue – Erik Jun 09 '21 at 21:16

score 6 · Answer 4 · answered Jul 13 '17 at 09:29

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.

score 2 · Answer 5 · answered Aug 31 '17 at 09:47

I agree with James.

I meet the same question as you after I install PYQT. After I uninstall pyqt by Pycharm's "Preference->Project:your current project->Project Interpreter" find pyqt and push '-' button, the debug works.

What is interesting is that when I run a script which includes 'from PyQt4 import QtGui'. The pyqt package installed auto. And the debug does not work again. So I uninstall pyqt again and debug works one more time!

So I think there may be some package make debug not work , what you should do is just find and uninstall it. The crime package is often the pyqt, matplotlib or something similary.

score 2 · Answer 6 · answered Aug 02 '18 at 13:58

2

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.

answered Aug 02 '18 at 13:58

Teddy Z.P.J.

101
3

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. – YohanK Dec 06 '18 at 09:36
The @re-gor solution worked once. I re-created my env and now I have no issues (at least few debugs) – visoft Sep 04 '19 at 10:02

score 1 · Answer 7 · answered Jul 19 '17 at 18:55

1

Mine worked after I removed pyqt5 bindings.

sudo apt-get remove python3-pyqt5

This wasn't happening to me because of building cpython. It was because I had installed an unrelated program. Hope it helps.

answered Jul 19 '17 at 18:55

James D

1,580
1
13
9

score 1 · Answer 8 · answered Dec 14 '18 at 20:14

1

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

answered Dec 14 '18 at 20:14

Edwin Evans

2,726
5
34
47

score 1 · Answer 9 · answered Dec 11 '22 at 22:21

1

I resolved this problem in 2022.3 by clearing the many breakpoints I had

answered Dec 11 '22 at 22:21

hasii

350
2
9

Amazingly this worked for me. – Fabio Apr 21 '23 at 13:08

score 0 · Answer 10 · answered Oct 25 '19 at 22:39

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

score -1 · Answer 11 · answered Nov 02 '17 at 15:34

-1

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

answered Nov 02 '17 at 15:34

user2579499

99

Pycharm debugger instantly exits with 139 code

11 Answers11

Linked