Note: relaunching from chrome://flags works but chrome://restart repros the issue (though the first manual launch following it worked this time).

Seems this isn't the first time relaunch breaks. If we fixed the installer tests to be able to launch chrome we could perhaps have a test for the relaunch scenario?

SyzyASAN canary crashes during startup on *some* but not all launches. I can repro with simple launch-quit-launch. Regular canary works fine. WER picks up the crash. In the event log, I see:

Faulting application name: chrome.exe, version: 54.0.2823.1, time stamp: 0x57a80e12
Faulting module name: chrome.exe, version: 54.0.2823.1, time stamp: 0x57a80e12
Exception code: 0xc0000005
Fault offset: 0x00075869
Faulting process id: 0x30dc
Faulting application start time: 0x01d1f1a9f64da95e
Faulting application path: C:\Users\grt\AppData\Local\Google\Chrome SxS\Application\chrome.exe
Faulting module path: C:\Users\grt\AppData\Local\Google\Chrome SxS\Application\chrome.exe
Report Id: 890ef4b1-8f9f-483d-8b20-478cf89b8f85
Faulting package full name: 
Faulting package-relative application ID: 

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: chrome.exe
P2: 54.0.2823.1
P3: 57a80e12
P4: chrome.exe
P5: 54.0.2823.1
P6: 57a80e12
P7: c0000005
P8: 00075869
P9: 
P10: 

Attached files:
\\?\C:\Users\grt\AppData\Local\Temp\WER78F7.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7937.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_chrome.exe_a21f42f0d47142993962fbdab57a4316155cd51_d99a9cd4_cab_03d27945\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_chrome.exe_a21f42f0d47142993962fbdab57a4316155cd51_d99a9cd4_cab_03d27945\triagedump.dmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_chrome.exe_a21f42f0d47142993962fbdab57a4316155cd51_d99a9cd4_cab_03d27945

Analysis symbol: 
Rechecking for solution: 0
Report Id: 890ef4b1-8f9f-483d-8b20-478cf89b8f85
Report Status: 4
Hashed bucket: 

A bisect range would be great in case this is a recent regression in SyzyASAN. Alternatively, is it possibly related to the Win10 refresh?

Tested the same by installing older buiilds and upon that overinstallng the new build manually and clciking refresh displays the relaunch button and on clicking it the chrome doesn't relaunch. O clicking the icon from taskbar it opens up.

This behaves similarly with the M53 builds as well. But working fine with M52 builds.
Tried with 52.0.2738.1  build and chrome relaunched successfully to 	54.0.2827.1.

CL : https://chromium.googlesource.com/chromium/src/+log/52.0.2741.0..53.0.2744.0?pretty=fuller&n=10000

Thank you tkonchada. Could you check the Windows event log to see if there are AppCrash events? To do so, launch "Event Viewer" then expand "Windows Logs" and look in the "Application" category for Information events from the "Windows Error Reporting" source and Error events from the "Application Error" source. Thanks.

This may also be related to issue 638370. The issue only happens with a 50% chance because of a 50% field trial that activates that code path. Does this match observations if repeatedly launched?

All I can say is that it's sporadic. Could be 50/50. I don't see the ASAN/Crashpad trial in chrome://version when it launches. Obviously I can't see the hashes when it doesn't launch. Is this a synthetic field trial? Is there a cmdline arg to force it?

(Sorry for ultra-slow delay, was traveling for 2 weeks of summit and training.)

Yes, this is a synthetic field trial. You can manually override the crash reporter in use via the environment, setting one of:

SYZYASAN_CRASH_REPORTER=crashpad
SYZYASAN_CRASH_REPORTER=kasko

Well, I can't repro at all in 55.0.2843.1. Hmm.

Is it still an issue?

Unable to repro with 56.0.2899.3. I'll re-open if I notice it again. Thanks for the ping.