Ambassador

It wasn't about git, svn or any other IDE plugin. It wasn't about "Live issues", or size of the project, nor about the Xcode preferences. It was about compiler warnings (simply; "issues"). I had to sample the Xcode process to understand what went wrong, after it started to consume 3.9GiB virtual memory. Turned out, Boost graph library has some unused variables and Xcode issued 999+ warnings (I didn't really count, but probably really very much, because it was in my precompiled header). I had to disable warnings for unused variables to fix the issue. I could have tried to fix the boost, but my simple grep didn't give me adequate result and I didn't want to go further; disabling warnings fixed my problem. The root of the problem is, I think, Xcode is trying to place those warnings in a hash table (or a multiset) and it takes obscenely high memory (3.9GiB in my case). Although I don't like Xcode at all, it's still good to be able to use it. My project itself has 2 warnings about pointer assignments (didn't really check, may be dangerous - I don't know yet). For the record, I have used some git performance tips I have found on the Internet as well. I think they helped the git itself, but I don't know whether it has any effect on Xcode performance.