Why a Single Warning Can Cause Xcode to Eat 6GB RAM – A Real‑World iOS Debugging Tale

Background

Team members reported Xcode consuming 6‑7 GB RAM on Macs with only 8 GB total, causing severe slowdown, while machines with 16 GB were fine.

Memory Comparison

After cleaning caches and compiling two nearby versions (812 and 816), the 812 build used about 2 GB, while the 816 build used about 6.8 GB.

Analysis Approach

Two possible methods were considered: (1) binary search through commits to locate the offending change, which is time‑consuming, and (2) investigate the memory increase directly. The team chose method 2.

Investigation Steps

Observed that Xcode kept ~1 GB memory after opening the project, rose to 2 GB during 812 debugging, and to 6 GB during 816 debugging, even after closing and reopening Xcode, indicating cached data.

Cache files are stored in /Users/<username>/Library/Developer/Xcode/DerivedData. Comparing the 812 and 816 caches showed the same number of files but a large size difference.

Each class generates three files: .o (object), .d (dependency list), and .dia (binary). The .dia files grew significantly.

Opening a .dia file revealed many nonnull warnings.

Root Cause

The project added a nonnull annotation to a legacy utility class containing 107 functions. This single change generated 107 compiler warnings, each stored in the .dia files. Because header files are referenced by many other files, the warning information was duplicated across thousands of .dia files, inflating them to hundreds of megabytes and causing Xcode’s memory usage to explode.

Resolution

The 107 warnings were fixed, the project was cleaned and rebuilt, and memory consumption dropped back to normal levels.

Takeaways

Never ignore warnings, especially in header files, as they can be propagated and cause large cache files.

Avoid importing headers within other headers to reduce transitive warning propagation.

Follow‑up

Version 818 removed all nonnull warnings; subsequent builds show reduced memory usage.