Re: Xcode 4.3.1 memory usage
Re: Xcode 4.3.1 memory usage
On 15 Mar 2012, at 15:56, Sean McBride wrote:
> On Wed, 14 Mar 2012 18:20:12 -0700, Brad Oliver said:
>
>> Just to be clear, my issue isn't really one of needing 16 GB baseline
>> for my build, it's that Xcode's memory usage creeps up so much during
>> the day that my cushion of 5 or 6 spare GBs dwindles to nothing and
>> provokes eventual swapping. Whether it's a true leak or very aggressive
>> caching, it's still a bit shocking to see so much memory vanish like that.
>
> You're able to run Xcode 4 throughout a whole day without it crashing? Cool. It's never run long enough for me to experience the kind of slow-leak-over-time problem you describe. Honestly, I'm jealous of your problem. :)
>
Personally I don't find ongoing leakage to be too much of a problem.
However even on an 8GB machine I do encounter problems with slow building on occasion with 4.3.1.
In particular, should anyone care to try and replicate this type of issue, I see very large memory usage when building F-script from https://github.com/mugginsoft/F-Script
This is a Lion friendly clone of the official F-script repo.
This one 4039 line file is the source of the trouble:
https://github.com/pmougin/F-Script/blob/master/FScriptFramework/FSObjectBrowserViewObjectInfo.m
clang Real Memory memory usage hits 4 to 5 GB when compiling this one file over a period of some 15 minutes or so.
If the build is cancelled before compilation completes then subsequent builds fail with a linker error:
file too small for architecture i386
This occurs because the generated FSObjectBrowserViewObjectInfo.o is of size 0 and the next build doesn't pick up that the compilation actually did not complete.
Normally the build stagnates with a displayed status of "Compiling 136 of 136 source files…".
The build log displays columns of nice green ticks.
However, scrolling back up the build transcript reveals a solitary grey arrow beside FSObjectBrowserViewObjectInfo.m indicating that that build is still in progress.
Eventually, however, the build does complete.
None of the above is indicative of any identifiable problem with the tool chain.
It just demonstrates that building can be lethargic.
It would be interesting to know how the build proceeds on a 16GB machine.
Regards
Jonathan Mitchell
Mugginsoft LLP
_______________________________________________
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