Issue metadata
Sign in to add a comment
|
Chrome won't start with --single-process flag
Reported by
runem...@gmail.com,
Dec 30 2016
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2967.0 Safari/537.36 Steps to reproduce the problem: Start chrome with the --single-process flag What is the expected behavior? What went wrong? Chrome immediately crashes and creates debug.log with the following lines: [1230/105718.397:ERROR:process_info.cc(608)] range at 0xdf241cba00000000, size 0x89 fully unreadable [1230/105718.397:ERROR:process_info.cc(608)] range at 0xdf241cda00000000, size 0x89 fully unreadable [1230/105718.397:ERROR:process_info.cc(608)] range at 0x0, size 0x89 fully unreadable Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? Yes Chrome version: 57.0.2967.0 Channel: canary OS Version: 6.3 Flash Version: Shockwave Flash 24.0 r0
,
Jan 4 2017
Single process not supported on Chrome looks to be an intended change. But launching the chrome with the flag silently crashes chrome and crash id is generated under chrome://crashes. Crash id: 2d24611080000000 Stack trace: ============= Thread 0 CRASHED [EXCEPTION_BREAKPOINT @ 0x00007ff9318c2934 ] MAGIC SIGNATURE THREAD Stack Quality100%Show frame trust levels 0x00007ff9318c2934 (chrome.dll -logging.cc:748 ) logging::LogMessage::~LogMessage() 0x00007ff9317f086f (chrome.dll -content_main_runner.cc:786 ) content::ContentMainRunnerImpl::Run() 0x00007ff9309a35d6 (chrome.dll -chrome_main.cc:85 ) ChromeMain 0x00007ff6d61273a8 (chrome.exe -main_dll_loader_win.cc:168 ) MainDllLoader::Launch(HINSTANCE__ *) 0x00007ff6d61220ce (chrome.exe -chrome_exe_main_win.cc:246 ) wWinMain 0x00007ff6d63ea4e2 (chrome.exe -exe_common.inl:253 ) __scrt_common_main_seh 0x00007ff95db28101 (KERNEL32.DLL + 0x00018101 ) BaseThreadInitThunk 0x00007ff95dc1c5b3 (ntdll.dll + 0x0005c5b3 ) RtlUserThreadStart Bisected this to find the exact change where this was introduced. Last good build: 33.0.1719.0 First bad build: 33.0.1720.0 Changelog: https://chromium.googlesource.com/chromium/src/+log/33.0.1719.0..33.0.1720.0?pretty=fuller&n=10000 Suspected change: https://codereview.chromium.org/65193003 for 'content_main_runner.cc' related change. dshwang@: Could you please take a look at this crash. Thank you!
,
Jan 4 2017
A bisect back to version 33 of Chrome is not useful. zmo@, didn't you explicitly fix single-process mode recently?
,
Jan 4 2017
Yes, but that's for content_shell. I didn't test for chrome.
,
Jan 11 2017
Gentle ping!! @zmo-- Any update on this ?? As per comment #3, considering this as non-regression issue and untriaging it. Thanks!
,
Jan 11 2017
Did you try --single-process with --disable-gpu-sandbox --no-sandbox?
,
Feb 13 2017
Just to update tried launching chrome by passing the parameters from C#6 and still Chrome didn't launch and it crashes silently. No crash id gets generated when launched chrome with parameters as mentioned in C#6.
,
Jan 10
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by ajha@chromium.org
, Jan 4 2017