On Mon, Nov 30, 2009 at 4:48 PM, Ted Mielczarek <ted.mielcza...@gmail.com>wrote:
> On Wed, Nov 25, 2009 at 7:42 PM, Wan-Teh Chang <w...@google.com> wrote: > >> (The official build does whole program optimization and must be >> done on a 64-bit Windows machine with lots of memory.) >> >> > Thanks for the info. That's odd, since our PGO builds don't use nearly that > much memory. I can build a PGO Firefox on a 32-bit WinXP box with 2GB of ram > without any thrashing. The linker tops out at a little over 1GB of memory > usage while linking libxul (using VC2005 or VC2010, with VC2009 I run out of > memory). I wonder what you're doing differently that requires that much > memory usage? > > Template usage? Maybe we hit a particular case that generates a symbols overflow. M-A -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev