search

sbinet / go-python

naive go bindings to the CPython2 C-API
Other
1.52k stars 138 forks source link

Process finished with exit code 137 (interrupted by signal 9: SIGKILL) #85

Open halegreen opened 5 years ago

halegreen commented 5 years ago

OS: mac air go version: 1.8

I run your example, but got this and nothing in output: what's the problem?

Process finished with exit code 137 (interrupted by signal 9: SIGKILL)
sbinet commented 5 years ago

that's a bit hard to tell, but from the signal, it would seem this is external to the process (ie: I'd believe it's the OS that has sent that signal and interrupted the execution of the program)

which example did you run? how?

Chuvantinh commented 4 years ago

I have same the output, I. think because the dataset are so big for the computation of computer then the computer must kill the process of algorithm automatic to protect device

amashi01 commented 4 years ago

In my case, memory usage was very high.

pwnedDesal commented 4 years ago

is there a way that allows the code to continue after exit code 137