In this article you can find solution for PyCharm Error:

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

If PyCharm's debugger instantly exits with code 139, it usually means a segmentation fault occurred. This is a low-level crash caused by:

  • native extensions
  • incompatible libraries
  • file/folder naming
  • or Python/IDE mismatches

Exit code 139 is common when debugging projects that use:

  • NumPy / SciPy
  • OpenCV
  • TensorFlow / PyTorch
  • C/C++ extensions
  • matplotlib
  • shorttext
  • Conda or custom Python builds

Below are the most common fixes.

Tips to solve the error

Exit code 139 = SIGSEGV (Segmentation Fault) on Linux and macOS.

Check if the error happens for:

  • another Python script
  • another project
  • different Python version or environment
  • different PyCharm version

PyCharm cannot catch this as a normal Python error.

Reproduce the Debug error

Try to debug the following code in PyCharm:

import shorttext
a = 1

it will show Colecting Data and later error in:

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

1. Quick Fix: Disable PyQt compatible

If you use gevent, eventlet, or Cython extensions, try disabling advanced debugger options:

In PyCharm:

  1. Go to Settings
  2. Build
  3. Execution
  4. Deployment
  5. Python Debugger
  6. Uncheck:
    • PyQt compatible

This often prevents segmentation faults during attach.

2. Check Python and PyCharm Compatibility

A common cause is using:

  • System Python with PyCharm
  • Conda Python with mismatched PyCharm helpers
  • Old PyCharm with new Python (or vice versa)

Fix:

  • Reconfigure interpreter in PyCharm
  • Reinstall PyCharm helpers
  • Make sure PyCharm supports your Python version

3. Remove Imported Libraries

Sometimes the imported libraries like shorttext might cause the debugging issues.

Library: https://pypi.org/project/shorttext/

4. Run Without Debugger to Confirm

Test if it only crashes in debug mode:

python your_script.py

5. Rename the file

Some reserved names might interfere with the debugger and cause problems:

  • types.py
  • String.py
  • site.py
  • inspect.py

Summary

If PyCharm debugger exits with code 139:

  • It is a segmentation fault (SIGSEGV)
  • Check compiled libraries (NumPy, OpenCV, etc.)
  • Reinstall or rebuild native packages
  • Verify Python–PyCharm compatibility
  • Disable advanced debugger compatibility modes

Resources