Re: Xcode performance issues over time
Re: Xcode performance issues over time
- Subject: Re: Xcode performance issues over time
- From: John Engelhart <email@hidden>
- Date: Fri, 12 Feb 2010 23:00:22 -0500
On Fri, Feb 12, 2010 at 11:55 AM, Brian Zwahr
<email@hidden> wrote:
Ok. I closed XCode, moved those files/folders, opened XCode, and created a new project. This still results in the same effect of XCode continuously using more and more memory.
I think I have traced the issue to the in-program editor. Once I set XCode to use a different editor (instead of XCode's built-in editor) I don't notice the issues.
IMHO, the "quality" of Xcode has been going down over the last year to year and a half. And by "quality", I mean that highly subjective "how it feels" to use for hours at a time. There seemed to be a noticeable down tick with 10.6 as well. Some times Xcode just seems to go out to lunch at times. I've actually gotten in the habit of killing off my Xcode sessions every few hours and restarting it because that "seems to improve things". I, too, have noticed that it's become a bit of a memory pig, particularly on 10.6. One quirk that's recently appeared is that the build system won't "catch" that I've modified a file. It's usually when I do a trivial modification, like I'm trying to hunt down a bug, and I comment out a single line and rebuild / run. The build progress window pops up, and "stuff happens", but every once in awhile it doesn't actually get around to recompiling the changed file. It looks like Xcode really re-compiled your changed code unless you carefully look at "what stuff is happening" during the build. I've unfortunately gotten in to the habit of very carefully going over the build results when debugging to make sure the changes I just made actually made it in to the program that I'm debugging.
There's really nothing more annoying than making changes to your source to see if it fixes the problem, still seeing the problem, and wasting a lot of time trying other things until you realize that a debug statement that can't possibly be executing because it's commented out but is STILL printing. And once you notice it, you make a trivial change to 'touch' the file, rebuild, and notice that the build system isn't compiling your changed file, even though "lots of stuff" seemed to happen. It's completely random and comes and goes, but "seems" to get worse the longer Xcode runs.
One thing you might try is disabling all "Message Bubbles" (i.e., warnings from the compiler for a given source line). This is under View > Message Bubbles > Hide Issues. For me, at least, turning off the bubbles dramatically increases the responsiveness of the editor. I also have my Code Sense / Code Completion auto-suggest set to "Never", but I can't remember if that's the default any more (though I have a faint memory of turning it off long ago).
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden