--type=crashpad-handler prevents chrome from opening in Windows 10

[cald...@alkamitech.com]

My chrome just updated to Version 58.0.3029.81 (64-bit) and the only way I can get chrome yo open is kill the chrome.exe process with crashpad-handler

Name PID Status Command line User name CPU Memory (private working set) Description
chrome.exe 11020 Running "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --type=crashpad-handler /prefetch:7 "--database=C:\Users\calderson\AppData\Local\Google\Chrome\User Data\Crashpad" "--metrics-dir=C:\Users\calderson\AppData\Local\Google\Chrome\User Data" --url=https://clients2.google.com/cr/report --annotation=channel= --annotation=plat=Win64 --annotation=prod=Chrome --annotation=ver=58.0.3029.81 --initial-client-data=0x248,0x24c,0x250,0x244,0x254,0x7ffba11229b8,0x7ffba1122980,0x7ffba1122990 calderson 00 2,504 K Google Chrome


Is there a command line switch I can use to disable crashpad-handler?
ie. --disable-breakpad

Are you aware of the issue?

Thanks in advance,
Chris

[Scott Graham]

Hi Chris,

I'm not aware of an issue that's stopping Chrome from starting based on blocking on the handler process. Could you file a bug at crbug.com/new?

--
You received this message because you are subscribed to the Google Groups "Crashpad-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crashpad-dev+unsubscribe@chromium.org.
To post to this group, send email to crashp...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/crashpad-dev/a6ffb5d6-9058-4d21-8148-14885acae12e%40chromium.org.

[Scott Graham]

Just came across some reports that might be relevant e.g. https://productforums.google.com/forum/#!topic/chrome/ghZAeFjO-V8;context-place=forum/chrome Are you using McAfee?

[Chris Alderson]

Yes, I work with Conner.

Thanks guys for all the help.

--

Christopher Alderson
Manager, QA Automation

Alkami Technology, Inc.
The Ultimate Digital Banking Solution
T: 877-725-5264 (x498) 
E: cald...@alkamitech.com 

[dpa...@gmail.com]

I'm on the latest version as of today (60.0.3112.101) on Windows 7 x64 and I'm having the exact same issue.

It happens both when I launch Chrome, and when I launch external Chrome apps (I use Google Keep).

In both cases, launching the shortcut causes this process to run, and nothing else happens until you use the task manager to kill it.
Once killed, the app (either Chrome, or the app) will start with no apparent issues.

The full command line (which I had to get from a memory dump, since it's too long to see in the task manager) is as follows:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --type=crashpad-handler /prefect:7 --monitor-self-annotation=ptype=crashpad-handler "--database=C:\Users\Username\AppData\Local\Google\Chrome\User Data\Crashpad" "--metrics-dir=C:\Users\Username\AppData\Local\Google\Chrome\User Data --url=https://clients2.google.com/cr/report --annotation=channel= --annotation=plat=Win64 --annotation=prod=Chrome --annotation=ver=60.0.3112.101 --initial-client-data=0x158,0x15c,0x160,0x154,0x164,0x7fee7aa29c0,0x7fee7aa29d8,0x7fee7aa29e8

[CruiserVonWard]

Same issue here, any fix?

[sbar...@gmail.com]

Same problem here.

[ramu.m...@gmail.com]

On Friday, September 8, 2017 at 8:28:40 PM UTC+5:30, Serge Baranov wrote:
> Same problem here.

Same problem for me too. I am using windows 7/64-bit OS with chrome version 61. Let me know if there is any solution. Basically this is preventing my automation scripts in chrome browser.

Regards
Rammohan

[Joakim Wallman]

This seem to be an old problem, but I'm still having this issue.

I think it started a year ago, and I have even changed computer in between, so I guess that there is some other process that cause the issue.

I have no problem on my home computer that are using the same google account (i.e. same plugins), but both my old and new work computer have the issue.

When I click a link in some other application like, Teams or pdf reader, nothing happens. But there is a chrome process created with crashpad-handler as an command line argument.

But it is not consistent, sometimes it works. Especially if I first kill all old Chrome processes.

I'm using lots of development tools on Windows 10 and using Webroot as antivirus SW.

If I set Microsoft Edge as default web browser it seem to work fine, but I prefer Google Chrome.

Is there a solution available for this problem?