iOS Build Environment Help Center

Insufficient Memory error during build

append delete MH6

TLDR: Insufficient Memory during build when you have plenty of RAM/storage is because one of your paths is hitting the Microsoft path length limit, which causes xcopy to fail.

I was going to post my issue here but after diagnosing it more and modifying the build.bat file I managed to figure it out.

I was getting "Insufficient Memory" during the Copying Resources stage of the build, which was perplexing because I had over 32GB RAM free and over 10TB of storage left. So I thought maybe it was a 32-bit issue and some process was hitting the 2 or 4GB hard limits, but nope. The same exact build & setup worked perfectly fine on my dev machine, and was only failing on the build machine.

So I started looking at the build.bat file, and found the Copy Resources stage which was utilizing xcopy. I took out the '> nul' bit in the xcopy command so I could see what file it was failing on, and turns out it was because good ol Unity Addressables creates gargantuan file paths by default. The oh so helpful "Insufficient Memory" error xcopy provides is actually because the file path is too long. So that's lovely.

I already knew long file paths were a nightmare in Windows so I try to avoid that when I can (the project folder was D:/XYZ/ so super short) but Unity of course decides to generate addressable asset paths that are hundreds of characters long.

I may just change the batch file to use robocopy as I believe that has no such limitation.

So anyway, if anyone else runs into this problem, and you have plenty of RAM/storage, it's the file path length limit causing it. I didn't see this posted anywhere so figured I'd leave it here for future readers.

Reply RSS

Replies

append delete #1. Pierre-Marie Baty

Thank you very much for this feedback. That xcopy command is a leftover from the days (10 years ago) where this toolchain still supported Windows XP. I could as well use robocopy indeed.

This is duly noted and will be done in the next release (very soon).

:: @Pierre-Marie Baty added on 08 Jun ’22 · 11:23

*edit* in the meantime, do you need help in patching you out of trouble ? Here's how I would do it: 

%
rem // NOTE: when copying a DIRECTORY, the copy would fail if the target directory already exists as a FILE, so make sure the target doesn't exist in any form first
rmdir /s /q "!TARGET!" > nul 2>&1
del /f /q "!TARGET!" > nul 2>&1
robocopy "!SOURCE!" "!TARGET!" /is /e /njh /ndl /nfl /njs > nul 2>&1
rem // do NOT check for errorlevel 0 as a success here : robocopy returns 1 when files were copied (and up to 7 means "success with warnings"). Microsofticly absurd, but that's the way it is...
%

:: @Pierre-Marie Baty added on 08 Jun ’22 · 11:33

P.S. for other readers: he was talking about version *3.49* of the builder.

Another illustration why posting the requested information when you create a new thread is important.

Reply

(Leave this as-is, it’s a trap!)

There is no need to “register”, just enter the same name + password of your choice every time.

Pro tip: Use markup to add links, quotes and more.

Moderators: Pierre-Marie Baty