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

Question

I\'m trying to execute a Python script, but I am getting the following error:

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


        

Answer 1

When I encounter this problem, I realize there are some memory issues. I rebooted PC and solved it.

Answer 2

I received the same error when trying to connect to an Oracle DB using the pyodbc module:

connection = pyodbc.connect()

The error occurred on the following occasions:

• The DB connection has been opened multiple times in the same python file
• While in debug mode a breakpoint has been reached while the connection to the DB being open

The error message could be avoided with the following approaches:

• Open the DB only once and reuse the connection at all needed places
• Properly close the DB connection after using it

Hope, that will help anyone!

Answer 3

After some times I discovered that I was running a new TensorFlow version that gives error on older computers. I solved the problem downgrading the TensorFlow version to 1.4

Answer 4

The SIGSEGV signal indicates a "segmentation violation" or a "segfault". More or less, this equates to a read or write of a memory address that's not mapped in the process.

This indicates a bug in your program. In a Python program, this is either a bug in the interpreter or in an extension module being used (and the latter is the most common cause).

To fix the problem, you have several options. One option is to produce a minimal, self-contained, complete example which replicates the problem and then submit it as a bug report to the maintainers of the extension module it uses.

Another option is to try to track down the cause yourself. gdb is a valuable tool in such an endeavor, as is a debug build of Python and all of the extension modules in use.

After you have gdb installed, you can use it to run your Python program:

gdb --args python <more args if you want>

And then use gdb commands to track down the problem. If you use run then your program will run until it would have crashed and you will have a chance to inspect the state using other gdb commands.

Answer 5

Deleted the python interpreter and the 'venv' folder solve my error.

Answer 6

This can also be the case if your C-program (e.g. using cpython is trying to access a variable out-of-bound

ctypedef struct ReturnRows:
    double[10] your_value

cdef ReturnRows s_ReturnRows # Allocate memory for the struct
s_ReturnRows.your_value = [0] * 12

will fail with

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