Re: 3.2 builds grind to a halt
Re: 3.2 builds grind to a halt
- Subject: Re: 3.2 builds grind to a halt
- From: Bjoern Knafla <email@hidden>
- Date: Tue, 29 Sep 2009 22:47:41 +0200
MacBook Pro 1Gen, 2 GB Ram - same effect (OS X 10.6.1, Xcode 3.2,
project format 3.2, projects build anew with Xcode 3.2). Trying to re-
build 4 files in a project (around 400 source files, C++, 10 external
static libs and frameworks) puts the machine to a halt and can take up
to 14 minutes. Same with 15 changed files that need a rebuild and I
force quit Xcode because I didn't want to wait.
From what I am observing these effects happen after Xcode was running
for some time (a few hours) and at least a dozen normal build-cycles.
Bjoern Knafla
On 29.09.2009, at 20:16, Steve Mills wrote:
I've been using 3.2 for a couple weeks now in 10.6(.1) on my octo-
core Mac Pro, gcc 4.2. Today, when I hit Build, it loads up 15 files
to compile, seems to begin compiling them (some warnings show up in
the build results), and then all my available RAM gets used up,
switching from about 75% active to about 50% active and 25%
inactive, and then the hard drive begins grinding and almost all
computer activity comes to a halt; very little screen updates, even
though things like my Activity Monitor CPU history icon and clock
should be moving. I've sat there for *minutes* waiting for at least
one of those files to complete compilation, but I always end up
canceling the build because it just should not take that long on a
modern Mac Pro with 8G of RAM.
Anybody else seeing 3.2 and/or gcc 4.2 being some sort of a huge hog
like this?
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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