The following build compiled successfully, so this could be a flake. See
https://build.chromium.org/p/chromium.win/builders/WinClang64%20%28dbg%29/builds/4506/

However, there is another bot with link failures: See also 	 https://crbug.com/638851 

Build 4509 failed in a similar way as build 4505.

Sample logs:
[643/5530] LINK remoting_breakpad_tester.exe remoting_breakpad_tester.exe.pdb
FAILED: remoting_breakpad_tester.exe remoting_breakpad_tester.exe.pdb 
C:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /OUT:./remoting_breakpad_tester.exe /PDB:./remoting_breakpad_tester.exe.pdb @./remoting_breakpad_tester.exe.rsp


  Version 14.00.23918.0



  ExceptionCode            = C0000005

  ExceptionFlags           = 00000000

  ExceptionAddress         = 000000013F1B1F6D (000000013F1A0000) "C:\b\depot_tools\win_toolchain\vs_files\95ddda401ec5678f15eeed01d2bee08fcbc5ee97\win_sdk\bin\..\..\VC\bin\amd64\link.exe"

  NumberParameters         = 00000002

  ExceptionInformation[ 0] = 0000000000000000

  ExceptionInformation[ 1] = 0000000000000008



CONTEXT:

  Rax    = 0000000005617AD0  R8     = 0000000000000000

  Rbx    = 0000000000000000  R9     = 0000000000000000

  Rcx    = 0000000204DFF728  R10    = 00000000069543E5

  Rdx    = 00000000001CE808  R11    = 0000000005617AD0

  Rsp    = 00000000001CE760  R12    = 0000000000000000

  Rbp    = 00000000001CE869  E13    = 0000000200400000

  Rsi    = 00000000001CE808  R14    = 0000000000000000

  Rdi    = 00000000026F6A90  R15    = 0000000000000000

  Rip    = 000000013F1B1F6D  EFlags = 0000000000010202

  SegCs  = 0000000000000033  SegDs  = 000000000000002B

  SegSs  = 000000000000002B  SegEs  = 000000000000002B

  SegFs  = 0000000000000053  SegGs  = 000000000000002B

  Dr0    = 0000000000000000  Dr3    = 0000000000000000

  Dr1    = 0000000000000000  Dr6    = 0000000000000000

  Dr2    = 0000000000000000  Dr7    = 0000000000000000

[644/5530] LINK it2me_standalone_host_main.exe it2me_standalone_host_main.exe.pdb
FAILED: it2me_standalone_host_main.exe it2me_standalone_host_main.exe.pdb 
C:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /OUT:./it2me_standalone_host_main.exe /PDB:./it2me_standalone_host_main.exe.pdb @./it2me_standalone_host_main.exe.rsp


  Version 14.00.23918.0



  ExceptionCode            = C0000005

  ExceptionFlags           = 00000000

  ExceptionAddress         = 000000013F1B1F6D (000000013F1A0000) "C:\b\depot_tools\win_toolchain\vs_files\95ddda401ec5678f15eeed01d2bee08fcbc5ee97\win_sdk\bin\..\..\VC\bin\amd64\link.exe"

  NumberParameters         = 00000002

  ExceptionInformation[ 0] = 0000000000000000

  ExceptionInformation[ 1] = 0000000000000008



CONTEXT:

  Rax    = 0000000005B6FD90  R8     = 0000000000000000

  Rbx    = 0000000000000000  R9     = 0000000000000000

  Rcx    = 00000002055CD928  R10    = 00000000057D43E5

  Rdx    = 000000000013EC98  R11    = 0000000005B6FD90

  Rsp    = 000000000013EBF0  R12    = 0000000000000000

  Rbp    = 000000000013ECF9  E13    = 0000000200400000

  Rsi    = 000000000013EC98  R14    = 0000000000000000

  Rdi    = 0000000002586A00  R15    = 0000000000000000

  Rip    = 000000013F1B1F6D  EFlags = 0000000000010202

  SegCs  = 0000000000000033  SegDs  = 000000000000002B

  SegSs  = 000000000000002B  SegEs  = 000000000000002B

  SegFs  = 0000000000000053  SegGs  = 000000000000002B

  Dr0    = 0000000000000000  Dr3    = 0000000000000000

  Dr1    = 0000000000000000  Dr6    = 0000000000000000

  Dr2    = 0000000000000000  Dr7    = 0000000000000000

I'm not really sure what you want the trooper to do in this case. The toolchain isn't owned by infra and this isn't happening on a particular machine.

Ben, this is the kind of bug that we end up pushing back on, FTR. Do we have a label we can put on issues like this? Should I pass this to the help list?

Maybe? I'm wondering if it's just clear that it's build related. It may be worth a discussion.

rnk, do you think your pdb size limit change might help with this?

It might help.

We could also be creating overly large symbol records, which we currently aren't checking for. I think we'll assert if our records are over 0xffff bytes (it will overflow a fixup), but we won't assert if our records are between 0xff00 and 0xffff bytes, and that might upset the linker.

If this is really a Pri-1, find an owner and update the priority.

This is the result of a bulk edit that moved high priority available bugs to a lower priority in an attempt to be more honest with bug filers.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Bruce has upgrade the VC linker a few times since this was reported, and I think we'll be moving to LLD eventually anyway. Either that or we fixed our codeview output.