Re: Xcode performance issues over time
Re: Xcode performance issues over time
- Subject: Re: Xcode performance issues over time
- From: Brian Zwahr <email@hidden>
- Date: Tue, 2 Feb 2010 12:40:23 -0600
Since I'm not exactly sure what you mean, I'm going to go with no. Do you mean running a Find (Command-F) on a whole project? If so, I never used find. I'm only doing small tutorial/learning programs, the current one only having 3 .h files and 3.m files. No need to run a find.
If Project Find means something else, please let me know.
Thanks!
Brian
On Feb 2, 2010, at 12:33 PM, Chris Espinosa wrote:
>
> On Feb 2, 2010, at 9:28 AM, Brian Zwahr wrote:
>
>> XCode becomes almost unusable after I use it for a while. Moving the cursor, resizing the window, etc. all take way too long. When I first open it (which opens quite quickly, actually), Activity Monitor shows it as using 100-120MB of memory and XCode works great. When I first start using it, this jumps to about 300MB but I barely notice a difference in performance. All well and good. However, this number increases over time, getting to over 1GB of memory used (haven't kept it open past that, because it becomes to slow to use). I have one project open. I have no more than 5 files "open" at a time (i.e. available in the editor pane's file history drop down select) and I use the all-in-one layout, so I only have one window open. Using other layouts doesn't effect the issue. Also, having other application's open or not makes no difference.
>>
>> Whenever I switch spaces (I keep XCode in its own space) to, say, use Safari and come back, XCode seems to use a little more memory. After little code changes (less than 20 lines added/modified) and several saves and build/runs, XCode keeps using more and more memory. I have garabase collection for the compiler set in the build tab of the project settings.
>>
>> I've seen other people ask about this on forums and such, and the only "solutions" I've seen are to keep less projects/windows open (which is impossible, as I have bare minimum), clean your targets (which doesn't help), and close/restart XCode (which does help, temporarily, but is not a solution nor should it be necessary).
>>
>> What could XCode be keeping in memory and is there a way to free some? Are these memory leaks in XCode? Does anyone else experience this slow down?
>
> Do you do a lot of Project Finds?
>
> Xcode caches the results of previous Finds for quick reference, but they add up over time. They should swap out to disk eventually, but it's a burden to carry them around. Open the Find Results smartgroup in Groups and Files and delete past Find Results to free up memory.
>
> s/XCode/Xcode/g
> s/effect/affect/g
> </pedantic>
>
> Chris
_______________________________________________
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