Handling OutOfMemory Errors

Sort of related to my post on externalizing memory settings for the buildAgents and TC Server, it would be nice if TeamCity would notice OOM errors in the build and handle appropriately (end the build as it would hang indefinitely) and similarly for a buildAgent which suffers from OOM errors. I know it is a tricky problem as your kind of hung by the time you get the OOM, but you guys are awfully clever and I'm sure you can come up with some way of dealing with OOM in a reasonable way.

--Tim

3 comments
Comment actions Permalink

Tim, that's good point and - I should agree - that's tricky problem. But please file a Jira request for that - we'll try to think about it and may be find a OOM error solution - at least for processes running on the build agent.

Regards,
KIR

0
Comment actions Permalink

Will do.

Clearly from my last two posts, I've been chasing around OOM errors. It's tricky because they could be coming from the build, the agent or the server. So anything to help alleviate the problem or to help track where it is coming from is a plus.

--Tim

0

Please sign in to leave a comment.