I forget what the memory usage was when 0.8 was cut, but around that time the compiler peaked at about 2.2 GB of memory. At this time, it would then fork to invoke the linker, which is the most common cause of the out of memory issues we've been seeing. For things like VMs, I've seen 4GB work pretty much all the time.
That being said, work went into recently reducing the peak, so now we peak at around 1.4GB instead, so if you compile on master with 3 GB of memory you may not see the failure. Data brought to you by the awesome folks managing http://huonw.github.io/isrustfastyet/mem/ :) On Fri, Oct 18, 2013 at 12:25 AM, Paul Nathan <[email protected]> wrote: > Hi, > > I have a 3GB Linux x64 machine that I've done occasional rust builds > on and I found it failing tonight: > > > task <unnamed> failed at 'failure in fork: Cannot allocate memory', > /home/rustbuild/src/rust-buildbot/slave/snap3-linux/build/src/libstd/run.rs:672 > > Is this to be expected? > > To be fair, I am using the machine for other things at the time - > compiling, internet browsing, etc. > > -- > Regards, > Paul > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
