Yes, --max-old-space-size comes up quite regularly, but it’s an option to tell Node the constraints of memory it can work within. Adding a huge figure wouldn’t help if this was a memory issue. As I mentioned previously, this doesn’t immediately appear to be a memory issue as the build completes, but with errors. Also, changing the plan changes the memory for the running instance, not the build container.
Please could you share some specific details of the issue you are experiencing that may help us troubleshoot it with you, e.g. any further logs/errors/output, service name/ID, other things you’ve tried, etc. If you don’t want to share these details on the community forum, please feel free to raise a ticket from the “Contact Support” link at the bottom of the Dashboard.
Alan