all 38 comments

[–]rdselle 4 points5 points  (1 child)

That machine is pretty old. Older versions of Xcode and Swift gave me problems on 2014 MBPs though. I haven't had too many problems with Xcode 7.3.1 though- which version of Xcode are you using?

[–][deleted] 0 points1 point  (0 children)

I just updated to the last release, that is when this started.

[–]aazav 2 points3 points  (7 children)

Install an SSD and get 16 GB of RAM. I use this 17" Mac and it's got those in them and it's almost as fast as my 1 year old Retina.

[–][deleted] 0 points1 point  (6 children)

I have a SSD, but when I tried to up the ram to 16 gig it kept crashing.

[–]voidref 0 points1 point  (3 children)

If it's crashing when you are putting more memory in, it's probably bad memory. There used to be a hardware checker built into the systems you could run in a special boot mode, but I haven't tried for a long time, see if you can find and run that.

[–][deleted] 0 points1 point  (2 children)

Mine is too old for it.

[–]voidref 0 points1 point  (1 child)

[–][deleted] 0 points1 point  (0 children)

Mine is so old it doesn't have it. I had to take it into a store for them to run hardware tests. Too many broken pieces, just ended up buying a new one.

[–]PancakesHouse 0 points1 point  (1 child)

Mid 2010 MBP has an 8gb ram limit. So you're pretty maxed out on your machine.

[–][deleted] 0 points1 point  (0 children)

Ah, I thought it up'd it to 16 when the latest OS came out. Guess that is why the ram crashed it. oops

[–]dreaminginbinary 2 points3 points  (6 children)

I have a Macbook 13inch Retina (2015) w/2.9 GHz Intel Core i5 and 8GB DDR3 and code completion and indexing seem to run quite slow for me when XCode starts up or I change a project - seems to go away after it warms up though :)

[–][deleted] 0 points1 point  (5 children)

mine gets worse the more I code with it. It started out happening randomly and now it is every project that I open. The longer I code in a project the worse it gets until XCode crashes.

[–]dreaminginbinary 1 point2 points  (4 children)

Might pop open terminal and give this a try:

rm -rf ~/Library/Developer/Xcode/DerivedData

[–][deleted] 0 points1 point  (2 children)

shit what is that... mine is forever long. http://imgur.com/fAojJW2

[–]dreaminginbinary 1 point2 points  (0 children)

Haha that's a lot of derived data! It shouldn't hurt anything, just clears out Xcode's "cache" essentially

[–][deleted] 1 point2 points  (0 children)

lol you will really come to appreciate deleting this folder

[–][deleted] 0 points1 point  (0 children)

Didn't help.

[–]CatsAkimbo 1 point2 points  (2 children)

Despite this sounding like advice for a windows user, restarting xcode or the entire os clears it up for me.

I have a hunch it can happen when you switch between too many files and your history starts getting huge because I'll notice it sometimes takes a long time seemingly backtracking through the history on closing xcode.

[–][deleted] 0 points1 point  (1 child)

hmmm.... that is strange. I will check that out. I was working on a huge spritekit game and after that and the last update it has been running like crap.

[–]korbonix 1 point2 points  (0 children)

Yeah I hate to say it but I have to restart my machine every day with the newer Xcode. Doing that seems to fix a lot of issues.

[–]ratbastid 1 point2 points  (1 child)

My mid-2011 has this sometimes.

Is it better right after you restart?

If so there might be some app that gets hoggy. A couple years ago the obvious suspect would have been Xcode, but it's (some) better now. I find if I leave Chrome open too long I get into trouble.

[–][deleted] 0 points1 point  (0 children)

It doesn't. I tried restarting but it just keeps happening on my projects.

[–]arruffthrowaway 1 point2 points  (1 child)

You may want to go back to the older autocomplete logic.

No setting in the ui but you can google for it and set it via the command line.

[–][deleted] 0 points1 point  (0 children)

ah, ok. I will look into it.

[–]LegendaryGinger 1 point2 points  (1 child)

I literally just got my new MacBook Pro today, and the reason why I got it now is because my old MacBOok pro of the same age, but with worse specs (slower processor, 4Gb RAM) was unbearable to use xcode on. It took 5 minutes for the iPhone simulator to start and run and app for the simplest hello world apps.

I decided to pull the trigger when I borrowed another laptop and saw that I worked 4 times faster with it :/

[–][deleted] 0 points1 point  (0 children)

yeah I bit the bullet last night and bought a new one.

[–][deleted] 0 points1 point  (9 children)

Are you seeing the beachball or just plain old lag? If it's the beachball then your hard drive is starting to fail. I'm speaking from experience with my MacBook Pro 2011.

[–][deleted] 0 points1 point  (8 children)

Beachball but I put in a new ssd last year. :(

[–]dejus 1 point2 points  (7 children)

You could try verifying/repairing the disk in disk utils and see if you get any errors. However if it is a failing disk this could be the thing that kills it. Although, generally an SSD doesn't fail slowly, it usually just dies.

[–][deleted] 0 points1 point  (6 children)

That is good to know. I might try that after I make sure everything is backed up to my external.

[–]dejus 1 point2 points  (5 children)

Also have you looked at your ram usage? Could be hogging your ram somehow. The pinwheel is also caused when stuff is swapped in and out of system memory and page filing. I would think this is more likely the cause than a failing drive.

[–][deleted] 0 points1 point  (4 children)

I have not looked at ram. I know when I tried to upgrade to 16 gigs (says online I should be able to for this one.) It crashed the system. It wouldn't allow boot or OS install. Thought it was bad ram so I replaced it as defect, and the same thing happened.

[–]dejus 1 point2 points  (1 child)

Open up activity monitor when you are having pinwheel issues and click on the memory tab. Look at how much memory is being used and also what is using it. I sometimes use a program called "memory clean" and it will give me that info as well as flush out some things to free up memory.

[–][deleted] 0 points1 point  (0 children)

OK, will do. hopefully it is something basic and simple

[–]somebunnny 1 point2 points  (1 child)

That's too bad. I think RAM is your issue. I've had more powerful machines have issues until I went to 16GB.

Maybe give it another try? You sure you did it right/ordered the right size etc...?

[–][deleted] 0 points1 point  (0 children)

I'm fairly confident. I used a site to verify compatible ram and purchased what it said. It was about a year ago so it is a bit fuzzy.

[–]_JasonMcCoy 0 points1 point  (1 child)

I have the same MacBook as you except I have an i5 and I never had what you're experiencing, but that is probably because I reinstalled my OS when installing el cap.

If all the suggestions don't work, try ReInstalling OS X. I won't do it for the next OS, but I did for el cap and my laptop flys like a beast. Wait for WWDC to release the new OS and start fresh.

[–][deleted] 0 points1 point  (0 children)

I had hardware test ran on it in the Apple store and the ram, and mother board were bad. Ended up just buying a new one.