Re: G4 867mhz, Leopard, and XCode 3
Re: G4 867mhz, Leopard, and XCode 3
- Subject: Re: G4 867mhz, Leopard, and XCode 3
- From: Greg Guerin <email@hidden>
- Date: Wed, 16 Apr 2008 22:47:38 -0700
Adam R. Maxwell wrote:
If anyone wants a fun test, try this (somewhat bloated) controller:
http://bibdesk.svn.sourceforge.net/viewvc/*checkout*/bibdesk/trunk/
bibdesk/BDSKEditor.m
After the #import statements at the top of the file, open a C
comment / * without a closing */ and start typing. It beachballs my
PowerBook and G5, and even a MBP 2.2 can't keep up with my typing.
This is with no other files open in Xcode.
Tried it on a Core 2 Duo Mac mini, 2 GHz, 1 GB RAM, with one core
turned off, OS 10.5.2. Xcode 3.0, 32-bit mode, predictive
compilation turned off (my normal settings).
Doing the actions exactly as you described, with syntax coloring
turned on (my normal setting), there's no question: it lags
horribly. It doesn't beachball, but it's waaaay sloooow.
However, when I turn syntax highlighting off, it becomes teh snappy.
Or if I leave syntax coloring on and close the comment with */, then
type more text inside the comments, it's also snappy.
Using Activity Monitor, syntax highlighting with an open comment
shows that it pegs the 1 core at 100% CPU until it catches up to my
typing. As it's catching up, there's still 420 MB free RAM (nearly
half what it has), and exactly zero disk activity. This means it's
not running out of RAM and it's not swapping. Instead, it appears to
be entirely tied up in syntax coloring of the open /* comment.
The most expedient work-around that preserves the most features
appears to be closing the comment.
Things that made no difference:
- enabling the 2nd core
- running Xcode in 64-bit mode
64-bit mode consumes more RAM, as expected, but there's still no
swapping.
-- 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