I think that not copying dbghelp.dll on Windows 7 and prohibiting is_win_fastlink on Windows 7 (how do we do that?) is, regrettably, the correct solution.

Just as a reminder...  I ran into another problem where blink was always re-linking and fast-link is the only thing that makes it bearable.

Brian: I think not using remove_webcore_debug_symbols=true is the solution to the always relinking thing. That should probably error out on Windows too.

Okay.  MSVC isn't going to be able to handle the Chrome binary for debugging, though.  Or most unittest binaries for that matter.

Is there a bug filed for the always re-linking? That should be fixed.

> MSVC isn't going to be able to handle the Chrome binary for debugging, though

Hmmm? I don't understand. I debug Chrome with MSVC all the time.

Also, I use component builds and I find that they re-link quickly enough, even without is_win_fastlink.

But, if you want goma and full symbols then you need is_win_fastlink and you may need to upgrade to Windows 10.

MSVC constantly crashes for me due to OOM errors.  Even attaching to a Chrome binary after loading only base.sln will consume 2.8G.

I recommend installing VS 2017 Update 3 Preview and using it for development. I have switched to it entirely. It fixes many OOM errors and, unlike previous versions of VS, if we promptly report problems with it then they may get fixed.

https://www.visualstudio.com/vs/preview/

It can side-by-side install with VS 2015 and VS 2017 (although it seems to reset some VS 2017 settings).

You can use VS 2017 for editing and debugging of binaries built with VS 2015. If you still hit OOM errors then let me know what gn args you are using as I have not had these problems.

Archiving P3s older than 1 year with no owner or component.