Comment 2 for bug 1581649

I don't think it's a ram issue. I ran "watch -n 5 'free -m'" in another terminal while running two executions (a completion and a failure). For the execution that passes, it lowers from 185m to 183m, during the failure it dropped to 154m and goes back up to 184m after the timeout error message occurs.