New issue
Advanced search Search tips

Issue 813674 link

Starred by 1 user
Status: Unconfirmed
Owner: ----
Cc:
vamshi.kommuri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug


Previous locations:
crashpad:218


Sign in to add a comment

Crashpad handler hangs in background process multiple times

Reported by nelsonro...@gmail.com, Feb 18 2018 
What steps will reproduce the problem?
1. Whenever chrome is closed, it keeps a chrome.exe --type=crashpad-handler process behind, even if "send usage statistics" and "run in background" are disabled. Since this happens every time chrome is closed, we end up with multiples process.

What is the expected behavior? What do you observe instead?
When chrome is closed, no chrlme.exe process should be left

What version of the product are you using? On what operating system?
Windows 10, Chrome version 64.0.3282.167 (Official Build) (64-bit)

Please provide any additional information below.

I noticed this does not happens when there is a background process called "Google Crash Handler". But since I have opted out of any usage statistics, I don't think this process should be running.

Thank you

Comment 1 by nelsonro...@gmail.com, Feb 18 2018 

Correction: issue continues to happen even with background process "Google Crash Handler". Please see attached screenshot. Chrome was not running in any way during that screenshot.

Thank you.
nIdW0v.jpg
251 KB View Download

Comment 2 by scottmg@chromium.org, Feb 20 2018 

Hi, thanks for the report. I'm going to move this bug to the Chrome bug database, as it's more likely a Chrome integration.

I don't know why chrome.exe --type=crashpad-handler is not shutting down, that's definitely a problem. The process will still be running even if you have opted out of all reporting though -- it still saves crash dumps to the local machine only.

"Google Crash Handler" is used by other products, for example googledrivesync, so that shouldn't affect Chrome's behaviour either way.

Comment 3 by scottmg@chromium.org, Feb 20 2018

Project: chromium
Moved issue crashpad:218 to now be issue chromium:813674.

Comment 4 by scottmg@chromium.org, Feb 20 2018

Components: Internals>CrashReporting
Labels: OS-Windows

Comment 5 by sindhu.chelamcherla@chromium.org, Feb 20 2018

Labels: Needs-Triage-M64

Comment 6 by vamshi.kommuri@chromium.org, Feb 21 2018

Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET TE-NeedsTriageHelp
As per comment #2 confirming this issue is related to crash handler, hence adding appropriate label for further triaging.

Thanks!

Comment 7 by benhenry@google.com, Jan 11

Labels: Pri-2
Issue has a component, but no priority. Updating to have default priority (Pri-2)
►

Sign in to add a comment