On Nov 4, 2009, at 9:58 AM, Stuart Smith wrote: I am using Xcode 3.1.3 on Mac OS X 10.5.8 with a project which is primarily written in C++ (parts are in C, ObjectiveC, and ObjC++).
I usually run my application in the debugger.
Lately, I’ve been having a problem where Xcode becomes unresponsive for thirty or more seconds, usually when it want to stop at a breakpoint. This is on a MacPro 4-core 2.66GHz. In Activity Monitor, I see that three cores are idle, and one core is at 100%. This also often happens when I quit the application.
I’ll willingly log a bug about this, but I’m asking here what information I can gather to go with the bug report. I have taken samples from Activity Monitor during the hang, but is there anything else I can do? The samples don’t tell me much – it looks like it is spending quite a while laying out text. I can’t post the sample to the list, it is too large.
Also, has anyone else seen such an effect and found a workaround? I’ve tried a clean build, that didn’t help.
thanks in advance for any insights,
I expect that it's loading the symbol files for your loaded libraries. It does this lazily, when you pause or hit a breakpoint, in order to speed up initial launch times.
Uncheck "Load Symbols Lazily" in Xcode > Preferences > Debugging. That will cause the 30-second hit at app launch, but thereafter, hitting the first breakpoint should not be delayed.
If the samples show it laying out text, then please file a bug with those samples at http://bugreporter.apple.com -- laying out text when hitting a breakpoint should not be any different than normal. But since that happens on the main thread, if there are other things starving the main thread of processor time, the sample may be misleading.
Chris |