Unable to reproduce the issue on Win-10 using latest canary #65.0.3293.0.
Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened Google Chrome Canary
2. Visited yahoo.com and did some debugging.
3. Closed the browser.
4. Observed that there was no GoogleCrashHandler64 process lingering.

anchangsi@ - Could you please check the screen cast and please let us know if anything missed from our side.

Thanks...!!

Deleted: 794264.mp4 6.5 MB

	794264.mp4 6.5 MB View Download

Thanks for looking into this.

I see that after you closed the browser, in the process list, we can still see "Google Crash Handler (32bit)" process. Why is that? Shouldn't it be closed?

Are you on 64-bit machine? If not, is that the reason why we couldn't see GoogleCrashHandler64, but saw "Google Crash Handler (32bit)" instead?

A little more details on our side: we run some automatic test scenarios which have Chrome involved. After the test run finished, we check if there is any additional processes lingering and found GoogleCrashHandler64. Since it's code-detected by the automatic test infrastructure in a timely manner immediately following the test run, if the process GoogleCrashHandler64 terminates itself only after a little while, it might have terminated by the time we manually inspect the task manager, hence not noticed.

This is probably not the case in your video though, I guess the "Google Crash Handler (32bit)" process is still in the task manager.

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Unable to reproduce the issue on Win-10 using latest canary #65.0.3309.4.
Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened Google Chrome Canary
2. Visited www.wikipedia.org and did some debugging.
3. Closed the browser.
4. Observed that there was no GoogleCrashHandler64 process lingering.
Note: The Win-10 machine used for testing is a 64-bit machine and the chrome used is also 64-bit. The Google Crash Handler (32bit) is seen even before doing debugging on a site.
Removing the Needs-Bisect label as it is not reproducible from TE-end and requesting someone from Internals>Core team to please have a look into the issue.

Thanks...!!

Deleted: 794264_issue.mp4 4.7 MB

	794264_issue.mp4 4.7 MB View Download

Can you suggest why there are "Google Crash Handler" and "Google Crash Handler (32bit)" in the task manager after the browser is closed? (your first video)

We want to understand whether our test has caused Chrome crash during the run. I appreciate that if some details can be disclosed on what the "Google Crash Handler" process does. Is it launched because there has been a crash? Or it is merely launched to prepare to capture a crash?

Also the "Google Crash Handler" in the video is the process's name, it's not the executable's name. By "GoogleCrashHandler64", we meant the executable name. It might just be the "Google Crash Handler" process.

Can anyone from Internals>Core please have a look into the issue as per comment #6 as that particular "GoogleCrashHandler64" which is an executable name is not seen lingering in system's task manager.

Thanks...!!

As per comment#5 and #7 it seems to be not reproducible from chrome chrome TE end. Hence adding TE-NeedsTriageHelp label. Could someone from dev team please have a look at this issue.

Thanks!

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!