On Wed, Jun 25, 2008 at 2:17 PM, Jaime Rios <[EMAIL PROTECTED]> wrote:
> Well,
> It's good to see that I'm not the only one having these problems. Turning
> off the syntax coloring helps, but Xcode still freezes when I am saving a
> file. This is on a brand new iMac 24" running 3GB of RAM and a 2.8
Well,
It's good to see that I'm not the only one having these problems. Turning
off the syntax coloring helps, but Xcode still freezes when I am saving a
file. This is on a brand new iMac 24" running 3GB of RAM and a 2.8 Intel
Core 2 Duo Extreme chip.
-Jaime
__
For more information you can read up on Time Profiling in the Shark
user manual, and specifically Windowed Time Facility (WTF).
Somewhere along the way someone ate my links. Thanks a lot, anonymous
gremlin. :)
Time Profiling: http://developer.apple.com/documentation/DeveloperTools/Conceptu
In any case, I'll definitely be filing a radar next time it
happens. Problem is, it's next to impossible get a repro the
problem given the number of variables (environment, SCM, project,
the file itself, and whatever UI actions/history that led up to that
point), so we come back to the str
What about dtrace on Leopard? Isn't it supposed to let you view
several aspects of program performance simultaneously, including a
stack trace? Maybe if you could tie where it consumes the CPU cycles
with the stack trace, it'll reveal a pattern? Just a thought.
On May 9, 2008, at 2:18 PM, L
