On Wed, Nov 25, 2009 at 7:42 PM, Wan-Teh Chang <w...@google.com> wrote:
> On Wed, Nov 25, 2009 at 4:22 AM, Ted Mielczarek
> <ted.mielcza...@gmail.com> wrote:
> > Hi,
> >
> > I couldn't find this info anywhere on the dev site (maybe I just
> > wasn't looking hard enough), but I'm curious as to what version of
> > Visual C++ you're using for the official Chrome builds.
>
> It's Visual C++ 2005.
>
> (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?
> I don't know if we'd seen similar problems with Breakpad symbols.
>
>
It's manifesting in our crash reports as truncated stacks, FWIW.
-Ted
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
