In the past couple of weeks, a certain build gets automatically canceled by TeamCity on a regular basis after running anywhere from 90 to 240 minutes. The entire build takes about 6 hours to run. It is run using several custom script build steps and fails at different build steps but tends to fail by the 3rd, 4th or 5th step. It hangs for an hour or more and then gets automatically canceled. We have seen this error in the build agent log:
[2015-03-03 15:37:12,727] out - Process exited with code 137
Here are the build failure conditions:
Does this seem like a memory crash? If so, why wouldn't the build fail rather than being automatically canceled?