• 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: Text Editing Slowness After Debugger Quits
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Text Editing Slowness After Debugger Quits


  • Subject: Re: Text Editing Slowness After Debugger Quits
  • From: j o a r <email@hidden>
  • Date: Sat, 18 Sep 2004 13:32:17 +0200


On 2004-09-18, at 06.45, Willy Pell wrote:

After closing the debugger on command line c++ projects, my primary
editing window gets really slow.  If I leave the debugger open, this
doesn't happen.

Have you tried manually closing any / all source files opened in the debugger editor before closing the window? When you close the debugger window it's just hidden, so it still sits there with all the files open. Xcode seems to be sensitive to having many files open - it keeps open editors in sync, et.c.


Also - _please_ run Shark / Sample / Spin Control and grab a report on what Xcode is doing when you notice this slowdown and send it as a performance bug report to Apple!

j o a r

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: 
 >Text Editing Slowness After Debugger Quits (From: Willy Pell <email@hidden>)

  • Prev by Date: Why does SCM have to be so ....... hard?
  • Next by Date: Re: Why does SCM have to be so ....... hard?
  • Previous by thread: Text Editing Slowness After Debugger Quits
  • Next by thread: Why does SCM have to be so ....... hard?
  • Index(es):
    • Date
    • Thread