Xcode 6: Build hangs and Interface Builder Cocoa Touch Tool starts allocating all RAM

Question

I’m having an issue to which I haven’t been able to find a solution just by searching here or on Google.

I’m building a project which is shared by multiple developer

Answer 1

I had two Xcode versions installed, 5 & 6. Not sure if this was the cause, but Apple indicated this does happen with people and that the appropriate action is to ensure that the correct version is 'selected'

xcode-select -p

Not sure this would have fixed the issue or not, but after removing both versions and then installing Xcode 6, things appear to have been resolved.

Answer 2

I had the exact same problem: opening the storyboard in xcode results in beach ball with the Interface Builder task consuming all the memory. I got it back working by editing the xml of the storyboard file and setting

useAutolayout="NO"

in the document node. Of cause this is not a solution to the problem (which seems to be a bug in xcode) because it screws all constraints, but at least I could open and compile the storyboard again.

Answer 3

I fixed the problem by changing the Builds For setting in the File Inspector for the storyboard from iOS6 & Later to iOS8 & Later It seems to work on iOS 7.0 & later, but changing it back to any of the iOS6 settings makes the problem recur.

Answer 4

I was getting the same "Compiling Storyboards" or "Compiling Asset Catalog" hang under Xcode 7.3.1. Activity Monitor showed multiple "Interface Builder Cocoa Touch Tool" processes running.

I was able to continue by:

1. Closing the offending storyboard
2. Closing the project
3. Restarting Xcode, but do not open the project
4. Open just the offending storyboard
5. Closing the storyboard and restarting Xcode
6. Open the project

Answer 5

This happens for me in Xcode 8.2.1 if I bind the wrong thing in a view-based table view (p.s., I'm using Core Data). I was binding the second-deepest-level Table View Cell view’s value to my array controller, when I should have been binding the text field to the Table Cell View, with a path of objectValue.<attributeName>. The column object should be bound to nothing, and the Table View Content should be bound to the array controller via arrangedObjects.

This, at least, works, and lets Xcode (ibtool) compile the storyboard without consuming all available memory and crashing the system.

Answer 6

I did a "binary search" to find which element was corrupting my .xib file.

Each time, I had to kill Xcode, delete Derived Data. Once I found the sub-view that was causing the problem, I removed and reconstructed it.