Died unexpectedly


#1

We have been noticing a lot of our builds have been dying unexpectedly recently. Sometimes a rebuild without cache solves the problem, sometimes not.

I just noticed in the last failure it says “Your build has exceeded the memory limit of 4G on 1 container. The results of this build are likely invalid. We have taken a snapshot of the memory usage at the time, which you can find in a build artifact named memory-usage.txt. The RSS column in this file shows the amount of memory used by each process, measured in kilobytes.”

Is this memory limit new? We have only recently begun experiencing this problem. The memory-usage.txt doesn’t give us any indication of what to fix, if anything?

Any suggestions on how to solve this?


#2