Seems related to a set of crash https://crash.corp.google.com/browse?q=stable_signature%3D%27MainDllLoader%3A%3ARelaunchChromeBrowserWithNewCommandLineIfNeeded-bf63224f%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:35

dont have access to the link 

i found the crash with app verifier tool and opening with debugger 

Thanks 

Could you provide more detailed repro cases? Without specific repro cases, there is little thing we can do. 

i used a mix of tools like Dr. Memory Appverifier Global flags and windbg 

1. Tried to instrument chrome.exe with Dr. Memory Which resulted in crash 
2. once Chrome crashed completely and on opening chrome resulted in Dead tabs only 
3. Then i used Appverifer with all tests enabled and found this bug 
4. its true dr. memory but helps tracing the real leaks also in some cases 

Error #1: UNADDRESSABLE ACCESS: writing 0x0000000000000000-0x0000000000000004 4 byte(s)
# 0 chrome.dll!GetHandleVerifier         +0x9dcd74 (0x000007fed8173ab4 <chrome.dll+0xa43ab4>)
# 1 chrome.dll!GetHandleVerifier         +0x9dcdb2 (0x000007fed8173af3 <chrome.dll+0xa43af3>)
# 2 ntdll.dll!RtlIsDosDeviceName_U       +0x267d   (0x000000007794616e <ntdll.dll+0x5616e>)
# 3 CRYPTBASE.dll!?                      +0x0      (0x000007fefd4d1081 <CRYPTBASE.dll+0x1081>)
# 4 ntdll.dll!LdrShutdownProcess         +0x1d0    (0x00000000779129b1 <ntdll.dll+0x229b1>)
# 5 ntdll.dll!LdrShutdownProcess         +0x1b8    (0x0000000077912999 <ntdll.dll+0x22999>)
# 6 ntdll.dll!RtlExitUserProcess         +0x8f     (0x00000000779127c0 <ntdll.dll+0x227c0>)
# 7 KERNEL32.dll!GetNumberOfConsoleFonts +0xce     (0x000000007781133f <KERNEL32.dll+0x4133f>)
# 8 KERNEL32.dll!CtrlRoutine             +0x1d2    (0x0000000077824c53 <KERNEL32.dll+0x54c53>)
# 9 KERNEL32.dll!BaseThreadInitThunk     +0xc      (0x00000000777e59bd <KERNEL32.dll+0x159bd>)


and 

Error #1: LEAK 256 direct bytes 0x0000000001dd4e60-0x0000000001dd4f60 + 0 indirect bytes
# 0 replace_RtlAllocateHeap               [d:\drmemory_package\common\alloc_replace.c:3770]
# 1 IsSandboxedProcess                   +0x4410b  (0x000000013f510370 <chrome.exe+0x90370>)
# 2 IsSandboxedProcess                   +0x44144  (0x000000013f5103a9 <chrome.exe+0x903a9>)
# 3 IsSandboxedProcess                   +0x49226  (0x000000013f51548b <chrome.exe+0x9548b>)
# 4 IsSandboxedProcess                   +0x47758  (0x000000013f5139bd <chrome.exe+0x939bd>)
# 5 IsSandboxedProcess                   +0x51a05  (0x000000013f51dc6a <chrome.exe+0x9dc6a>)
# 6 IsSandboxedProcess                   +0x474fc  (0x000000013f513761 <chrome.exe+0x93761>)
# 7 IsSandboxedProcess                   +0x4795d  (0x000000013f513bc2 <chrome.exe+0x93bc2>)
# 8 IsSandboxedProcess                   +0x36110  (0x000000013f502375 <chrome.exe+0x82375>)
# 9 IsSandboxedProcess                   +0x3613c  (0x000000013f5023a1 <chrome.exe+0x823a1>)
#10 IsSandboxedProcess                   +0x36259  (0x000000013f5024be <chrome.exe+0x824be>)
#11 IsSandboxedProcess                   +0x47cb8  (0x000000013f513f1d <chrome.exe+0x93f1d>)

Error #2: POSSIBLE LEAK 88 direct bytes 0x0000000001dfb7e0-0x0000000001dfb838 + 1 indirect bytes
# 0 replace_RtlAllocateHeap                     [d:\drmemory_package\common\alloc_replace.c:3770]
# 1 ntdll.dll!RtlGetOwnerSecurityDescriptor    +0x255    (0x00000000778f87c6 <ntdll.dll+0x87c6>)
# 2 ntdll.dll!RtlGetOwnerSecurityDescriptor    +0x14c    (0x00000000778f86bd <ntdll.dll+0x86bd>)
# 3 ntdll.dll!RtlUserThreadStart               +0x9e     (0x000000007791a35f <ntdll.dll+0x2a35f>)



as above example

which helps finding the crash point with offset  

with Appverifier it crashed with 

APPLICATION_VERIFIER_LUAPRIV_FAILED_API_CALL (332e)
The application called an API that failed unexpectedly, possibly due to bad parameters.
The application called the listed API, which failed with an access error suggesting a potential LUA issue. 

Without a concrete repro (for example start up command line argument, or a webpage/script causes crashing), there is very little things I can use to reproduce this issue.

We'll keep on monitoring crash caused by RelaunchChromeBrowserWithNewCommandLineIfNeeded. But for now I'll close this bug. 

 

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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