On 9/29/09 1:16 PM, Steve Mills said:
>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?
We saw the same thing (or something similar) this spring in the 10.6 seeds.
<rdar://problem/6831962>
10a335: Xcode quickly saturates physical RAM and CPU cores while compiling .mm
Basically, the system uses about 700 MB RAM per instance of gcc. So on
an 8 core machine you can exhaust RAM easily, then you swap to death. Try:
defaults write com.apple.Xcode PBXNumberOfParallelBuildSubtasks 2
to see if this works around the problem. My solution was to buy
craploads of RAM! Solved the problem nicely. :)
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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
