Hiya @TK1,
Hard to tell exactly what is happening, without a specific deploy to look at. Mind sharing a recent deploy ID that failed (last part of the URL in our UI’s deploy logs URL for that deploy), so we can check memory usage in our monitors to confirm? In the future, if you’ll link to your deploy logs instead of (or in addition to) copy-pasting them, that will help us help you more quickly.
But that message about running out of memory comes from your code (that is not a message Netlify is trying to send to you from our systems). Naively, it seems like your build process is waiting for something that is in this case crashing - yet it doesn’t “respect” the failure correctly, and abort the build process right then. That, you’ll need to fix for yourself in your build pipeline, once we’ve confirmed your suspicions that the error message is correct. This workflow I link below is kind of related to that, and you could use a similar pattern to ensure your build actually exits when it encounters a fatal error, so it doesn’t run for another 40-45 minutes (until your timelimit passes):