Same commit - sometimes out of memory, sometimes just fine

Josh Zacharias's Avatar

Josh Zacharias

04 Jul, 2019 09:08 PM

Today I have been struggling to get my old angular 4 app building successfully because it has gone through the whole morning running out of memory with a:
"FATAL ERROR: Scavenger: semi-space copy Allocation failed - process out of memory"

However, after trying various configurations of memory allowance I came back to that same commit out of frustration and rebuilt. To my surprise it succeeded!

Although I am pleased that I am no longer wasting my time on this, I want to understand why this happens. Are some build machines more memory restrained than others? How can I ensure my builds are run on machine with enough memory?

  1. Support Staff 1 Posted by Feodor Fitsner on 05 Jul, 2019 05:01 PM

    Feodor Fitsner's Avatar

    We indeed upgraded virtualization hosts recently and added more memory (and put NVMe drives). Now VMs start with 5 GiB of RAM which can grow to 6 GiB.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac