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, Lyndsey Ferguson wrote:
On May 9, 2008, at 11:51 AM, Andy O'Meara wrote:
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 strange fact that only certain
projects seem to be affected.
When ever I want to submit bugs to Apple regarding Xcode's
performance, I keep SpinControl running with a focus on Xcode. That
generally generates enough files to submit.
Lyndsey
---
Mr. Lyndsey Ferguson
[EMAIL PROTECTED]
http://winterlandexpat.blogspot.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list ([EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/wsquires%
40satx.rr.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
