jschuh, brucedawson, wfh: we're seeing multiple instances of the browser crashing upon startup, unfortunately without producing a minidump:

https://ci.chromium.org/buildbot/tryserver.chromium.win/win_optional_gpu_tests_rel/?limit=200

Has this been seen on other Windows bots?

Strangely, the same problem doesn't seem to happen on:
https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/?limit=200

Also not seeing it on:
https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win7%20Release%20%28NVIDIA%29/?limit=200

Could these all be the same person's tryjobs?

Could a CL have been committed to ANGLE recently which could have caused, maybe, an early GPU process crash which somehow causes the browser to crash?

I see the following from https://ci.chromium.org/buildbot/tryserver.chromium.win/win_optional_gpu_tests_rel/17179 and https://chromium-swarm.appspot.com/task?id=39de7b8a4fc72c10&refresh=10&show_raw=1 in particular:

********************************************************************************
	Last event: 11e0.bd0: Break instruction exception - code 80000003 (first/second chance not available)
	  debugger time: Thu Nov 16 08:30:49.982 2017 (UTC - 8:00)
	ChildEBP RetAddr  Args to Child              
	003cf138 6c7add4f 00000000 00000000 00000000 chrome!base::win::RegisterInvalidParamHandler+0x21
	003cf154 6a1b80be 027c0270 00000001 027be2e4 chrome!_invalid_parameter_noinfo_noreturn+0xf
	003cf168 6b324c3a 0097ab4c 00000030 027a3c80 chrome!std::vector<display::Display,std::allocator<display::Display> >::_Tidy+0x62
	003cf300 6b323579 003cf320 6a0a0df6 003cf320 chrome!display::win::ScreenWin::UpdateFromDisplayInfos+0x444
	003cf350 6b323491 003cf2ec 027a3c84 003cfde8 chrome!display::win::ScreenWin::Initialize+0xcf
	003cf424 6b3233c5 00000001 027a3c80 003cf440 chrome!display::win::ScreenWin::ScreenWin+0xc7
	003cf434 6c10611d 01014b00 003cf458 6bdb9ede chrome!display::win::ScreenWin::ScreenWin+0xd
	003cf440 6bdb9ede 01016d00 a12229a7 01016d00 chrome!views::CreateDesktopScreen+0x17
	003cf458 6aa6dc7e 01016268 00000000 003cf48c chrome!ChromeBrowserMainExtraPartsViews::PreCreateThreads+0x20
	003cf548 6aa61c3e 01016d00 01002750 6c983bad chrome!ChromeBrowserMainParts::PreCreateThreads+0xd2
	003cf5a8 6a3d83c7 01013710 00000040 003cf5d0 chrome!ChromeBrowserMainPartsWin::PreCreateThreads+0x146
	003cf648 6a6ef048 01017860 01013710 003cf674 chrome!content::BrowserMainLoop::PreCreateThreads+0x53
	003cf660 6a3d8a88 01013710 6a3d9f38 01013710 chrome!content::StartupTaskRunner::RunAllTasksNow+0x1e
	003cf760 6a3dce79 6c97ab4c 003cf768 00000002 chrome!content::BrowserMainLoop::CreateStartupTasks+0x278
	003cf7d4 6a3d71fc 003cf908 003cf7f0 6aac245c chrome!content::BrowserMainRunnerImpl::Initialize+0x213
	003cf81c 6a9db2ec 003cf908 6ab5fece 01000000 chrome!content::BrowserMain+0x88
	003cf8ec 6a9db84c 003cf920 003cf908 003cfb74 chrome!content::RunNamedProcessTypeMain+0xec
	003cf9e8 6a9f242f 003cf938 00000003 003cfb08 chrome!content::ContentMainRunnerImpl::Run+0x116
	003cfaf8 6a9db1d9 003cfb04 003cfb08 6c940a70 chrome!service_manager::Main+0x2a3
	003cfb38 69fe119c 003cfb5c 003cfb44 003cfb40 chrome!content::ContentMain+0x31
	*** WARNING: Unable to verify checksum for chrome.exe
	003cfba8 011b5234 011b0000 003cfbf0 c631d384 chrome!ChromeMain+0x120
	003cfc34 011b154f 011b0000 c631d384 00000004 chrome_exe!MainDllLoader::Launch+0x22e
	003cfdac 01294448 011b0000 00000000 00432848 chrome_exe!wWinMain+0x54f
	

It's a little disappointing that we didn't receive any traction in investigating this, but the problem seems to have mysteriously gone away. In recent builds:
https://ci.chromium.org/buildbot/tryserver.chromium.win/win_optional_gpu_tests_rel/?limit=200

the two problems appear to be:

1) Git repos being unavailable -- this is an infra issue being worked on, possibly already solved.

2) A couple of VMs seeming to have corrupted checkouts or builds -- filed Issue 786463 about this.

Closing as WontFix -- no longer happening.