• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 2.1 saving lag
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.1 saving lag


  • Subject: Re: Xcode 2.1 saving lag
  • From: Scott Tooker <email@hidden>
  • Date: Thu, 16 Jun 2005 11:38:26 -0700

In all these cases the best thing to do is sample Xcode when it is being slow (using Sahrk, Sampler, or Spin Control) and file bugs.

Scott

On Jun 16, 2005, at 11:13 AM, Nick Nallick wrote:

Since I grew up using Microsoft Word and the like, it's become second nature for me to press command S to save every few seconds (instinctively). However, since upgrading to Xcode 2.1, I've noticed a huge lag whenever I said. I even get the spinning beach ball. Is there some new setting in Xcode that causes it to do something wacky and compute intensive on save?


It's doing three things:

1) It's recalculating the dependency tree to mark dependent files and targets as dirty and needing a rebuild. We know this process is unoptimized and are working on it.

2) It's reindexing that file. This happens on a lower-priority background thread and shouldn't take too long or be noticeable.

3) It's actually compiling the file in the background for you, in case that's the next thing you'll be doing. Again, this happens on a low-priority background thread. If you have a low-memory machine this may cause swapping and result in a spin, but if you have more RAM this is not noticeable

4) It's unfortunately doing a full text layout of the entire file. This is only noticeable in very large files, but is an optimization opportunity for us.

My guess is that you have a large dependency tree, and that you're running into 1).


I see this problem when saving a file after fixing compiler errors. For some reason when editing the files local to my project there are markers in the vertical scroll bar of the editor window to show where errors and warnings are, but the the files I'm referencing from a library folder outside of my project don't contain these markers. The files with the markers take an extra few seconds to save, but the files without markers save normally. Therefore I suspect the lag is due to the editor updating the marker locations.


Regards,
Nick Nallick
_______________________________________________
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


_______________________________________________ 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
References: 
 >Re: Xcode 2.1 saving lag (From: Nick Nallick <email@hidden>)

  • Prev by Date: Re: PRODUCT_NAME question
  • Next by Date: Re: CopyCStringToPascal
  • Previous by thread: Re: Xcode 2.1 saving lag
  • Next by thread: .xcconfig files
  • Index(es):
    • Date
    • Thread