I’d be interested to hear if this revert has also solved the OP’s problem. The OP (@devnull ) reported seeing
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
which wasn’t reported by @pfaffman
Also I’d like to comment on this:
Adding RAM can sometimes improve performance, but for actually running out of memory, what counts is RAM+swap. If adding swap doesn’t help with an out of memory condition, then adding RAM won’t either.
As @weallwegot reports the failure persists even after adding 4G of swap, something is (or was) very hungry indeed.