Skip to content
This repository has been archived by the owner on Jul 24, 2023. It is now read-only.

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

Open
halegreen opened this issue Jun 13, 2019 · 4 comments
Open

Comments

@halegreen
Copy link

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
Copy link
Owner

sbinet commented Jun 14, 2019

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
Copy link

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
Copy link

In my case, memory usage was very high.

@pwnedDesal
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants