Hey Apple Team!
We recently updated to Xcode 16 and saw a massive memory spike, which caused "Out of memory" Mac warnings in the final stages of our app's build process.
We noticed that the process responsible for this is "EmbeddedBinaryValidationUtility" (see screenshot).
Is there a workaround to limit its memory usage? This is causing significant anguish for our developers.
I can confirm this is also happening to me. Multiple times a day, whenever I build my project, just using one simulator. Even after clearing derived data, even after restarting my laptop. I'm on an M3 with 36 GB memory.
Seeing this as well. Updated to Xcode 16.2 and had at least 3 instances of "Out of Memory" freezes.
Working with a Apple M3 Pro with 36GB memory.
I have been experiencing the same issue the past couple of days. Xcode 16.2 is causing serious memory issues on my M3 Pro (36GB RAM). I only have 3 simulators installed (iPhone 16, 16 Plus, and 16 Pro all with iOS 18.3.1). Memory usage spikes over 20GB during build/run, and I've even seen it reach 62GB, leading to multiple system restarts.
This is happening to me as well!
This is happening to me as well - even to the point that the (one year old) laptop will freeze and restart.
Thanks for bringing this to our attention! We're tracking this problem and will update this thread when a fix is available.
A workaround that so far seems to be working for me is to replace embeddedBinaryValidationUtility with a no-op shell script. I'm not sure what this validation is exactly meant to do but for regular dev builds to the simulator and at least in the (very large) project I work with daily, it seems we can live without it.
cd /Applications/Xcode-16.2.0.app/Contents/Developer/usr/bin
mv embeddedBinaryValidationUtility embeddedBinaryValidationUtility-copy
cat <<EOF > embeddedBinaryValidationUtility
#!/bin/bash
exit 0
EOF
chmod +x embeddedBinaryValidationUtility
Indeed, our current workaround was to create an executable with the same name that exits with 0.