Re: Xcode eats 100% CPU and more while typing
Re: Xcode eats 100% CPU and more while typing
- Subject: Re: Xcode eats 100% CPU and more while typing
- From: Greg Guerin <email@hidden>
- Date: Tue, 5 Feb 2008 10:34:06 -0700
Axel Balley wrote:
>It really seems to have to do with CodeSense since sampling XCode shows
>that it is tokenizing and parsing my code during those spikes. Maybe it has
>to do with the trouble CodeSense has with C++.
Here's a test: turn off indexing. Don't panic. This is only a test.
The goal is to determine the actual cause of the problem, before attempting
to solve the problem.
Earlier, there were two obvious possibilities: predictive compiling and
indexing. If it's not predictive compiling, the remaining obvious
possibility is indexing. So turn off indexing, and see if the CPU usage
drops. If it doesn't, then it isn't indexing, but something less obvious.
If the CPU usage does drop, then we can address the indexing problem. But
until it's clear that it's indexing, you're just guessing.
>It would be really nice to hear from Apple on this.
I think they would tell you to turn off indexing, and if it solves the
problem, file a bug-report with a well-isolated fail case that includes the
files that cause the problem in indexing.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden