When opening Chrome it immediately crashes/closes
Reported by
justinaj...@gmail.com,
Nov 8 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36 Steps to reproduce the problem: 1. deleted chrome policy registry keys application still crashed 2. deleted user data folder and application did not launch 3. uninstall/re-install application it did not launch 4. Added --disable extensions to shortcut and application launched What is the expected behavior? For application to launch load the plugins What went wrong? We're deploying Chrome for work to all computers in our environment, however for some reason when Chrome is launched it immediately closes.It seems as if it is trying to load extensions then closes before completion. We are using GPO to enable several extensions such as Acrobat and IE Tab. If we add --disable extensions to the shortcut chrome works fine but is not ideal when we have apps that depend on those extensions. Whenever the application crashes it adds information to C:\Program Files (X86)\Google\Chrome\Application\debug.log file which really doesn't help me out very much since I googled the error and nothing useful came up. This happening in both Windows 7 x64 and now Windows 10 x64 as of late using Google Chrome 62.0.3202.66 x64. This issue has been happening since Chrome 54. Crashed report ID: 568353a6-b497-483e-99c7-e94c07109d38 How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 62.0.3202.62 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 27.0 r0 debug.log [1103/150131.571:ERROR:process_info.cc(632)] range at 0x188e244600000000, size 0x1e6 fully unreadable [1103/150131.572:ERROR:process_info.cc(632)] range at 0x188e246600000000, size 0x1e6 fully unreadable [1103/150131.572:ERROR:process_info.cc(632)] range at 0x0, size 0x1e6 fully unreadable
,
Nov 9 2017
Re c#1: I doubt they have anything in common. Can you try running Chrome with --enable-logging and then seek out the chrome_debug.log file which will be created in the User Data folder. It should have more information than what you are seeing in the debug.log Also when you run Chrome with --disable-extension please navigate to chrome://crashes (provided you have crash reporting turned on in the browser settings) and share some of the server id-s of crashes that the browser should have gathered. Even if you don't usually run with crash reporting turned on please enabled them for the sake of collecting some samples of the problem. @grt: I remember you once mentioned that the fact that debug.log is written at all means that we invoke LOG macros before the default output is even correctly specified. This sounds fishy already to me. @devlin: FYI since this seems to be extensions related issue.
,
Nov 9 2017
Those log messages are from crashpad (related issue 715061). It would be great if we could see the generated crash dumps.
,
Nov 9 2017
,
Nov 10 2017
Regarding comment 3, those log messages appear because Chrome has crashed. They are not a sign of a problem with Chrome, but rather ordinary log messages produced by crashpad as it is handling the crashing Chrome. Do you find any dmp files in "%localappdata%\google\chrome\user data\crashpad\reports"?
,
Oct 29
No recent activity, archiving |
||||
►
Sign in to add a comment |
||||
Comment 1 by manoranj...@chromium.org
, Nov 8 2017Components: Enterprise