Setting Breakpoints in XCode - Comically slow
Setting Breakpoints in XCode - Comically slow
- Subject: Setting Breakpoints in XCode - Comically slow
- From: Adam Hall <email@hidden>
- Date: Sat, 29 Sep 2007 05:56:27 -0400
Setting a breakpoint in XCode 2.4.1 , I see a jump from 1% - 100% CPU
(say hi to the spinning beach ball) and the whole process takes
around 8-10 seconds to set ONE breakpoint. This is on a G5 with 2
gigs of memory and around 800mb free ram.
Is anyone else seeing this sort of thing? I am asking here because I
am assuming there is just something wrong on my machine, I cant
believe something would ship with this sort of blocking code. I
noticed something else, when Xcode says Checking Dependencies , its
blocking for me in this case as well! The whole interface is locked
with a spinning beach ball. This effects the entire XCode
application including any separate projects that may be open, the
whole UI is frozen dead until its done checking dependencies. Now,
this may not be a big deal on small projects, but I have a large
project and this can take into the minutes with Xcode being totally
locked when certain files are edited. I might be able to work around
so its not constantly checking so many dependencies but what the heck
is the deal with this? Once again I can't believe they would release
like this (how hard is it to make a thread!?!?) , so I am a little
worried about my system having a more serious issue. I will check out
XCode with some debugging tools to see what is going on, but thought
I would mention these initial observations and see if its just my
machine or if these are well known problems.
Regards,
Adam
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden