Xcode 7.1
Server v 5.0.10
Mac OS 10.11

If any of you recall, I had an odd and intermittent error on our super slow 
Xcode build server where build errors would happen when trying to build xibs.  

The "Interface Builder Cocoa Touch Tool" times out trying to launch and this 
generates a build error.

Now, I added another project to our build server and guess what, this same 
issue is happening intermittently again.

What I'm pretty sure of is that this is an artifact of that fact that I am 
using a Mac mini that I had lying around with 4 GB or RAM.  (It's the base 
model.)   What I see often on the device when I use it is the older spinning 
blue pinwheel that appears over the spinning technicolor pinwheel of death.

At this point, since this is El Capitan and V10.11 of the Mac OS, I am assuming 
that memory is being shifted and compressed.

I'm pretty sure that this new memory compression is causing this.  So, two 
questions

1. Memory compression in Mac OS.  Can this be turned off?  Actually, it's also 
causing massive performance problems on my 16 GB iMac as well but I'm not 
seeing the spinning technicolor pinwheel of death, just terrible performance 
ever since I upgraded on multiple systems.  

2. Is there a timeout parameter that can be changed in a settings file that 
says how long the Interface Builder Cocoa Touch Tool has to launch or whatever 
tool (launchd?) that launches it has to wait until a process times out when 
launching?

This is a simple timeout issue that breaks our builds on a regular and 
intermittent basis

It would be nice to have a build server that works reliably and sadly, a 
studlier machine is not in our budget at the moment.

Thanks in advance,

Alex Zavatone
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to