Process terminated by exit code 137 in PyCharm

When I stop the script manually in PyCharm, the process exits with exit code 137. But I did not stop the script. Still got exit code 137. What's the problem?

Python version 3.6, the process terminated when the xgboost.train () method was run.

+24
source share
4 answers

Exit code 137 means your process has been killed (signal 9) by SIGKILL . In case you manually stopped this - there is your answer.

If you did not stop the script manually and still received this error code, then the script was killed by your OS. In most cases, this is caused by excessive memory usage.

+16
source

Got an error when to do:

 for i in range(1 << 35): 
0
source

I had the same error. In my case, this was due to excessive memory usage. Solved after flushing / clearing my cache data, adding the following code for each variable that will no longer be used:

 MyVariableName = None 
0
source

This is not always a memory problem. In my case, subprocess.Popen used, which threw an error of 137, which looks like signalKILL, and the reason is definitely not in memory usage, because at run time it almost did not use 1% of memory usage. This seems to be a resolution issue after further investigation. I just moved the scripts from /home/ubuntu to the root directory.

0
source

Source: https://habr.com/ru/post/1266450/


All Articles