Skip to content
This repository was archived by the owner on Jul 24, 2023. It is now read-only.
This repository was 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

Description

@halegreen

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) 

Activity

  1. sbinet commented on Jun 14, 2019

    @sbinet
    Owner

    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?

  2. Chuvantinh commented on May 15, 2020

    @Chuvantinh

    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

  3. amashi01 commented on May 27, 2020

    @amashi01

    In my case, memory usage was very high.

  4. pwneddesal commented on Jun 8, 2020

    @pwneddesal

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions