This crash has spiked a lot on latest Chrome Stable i.e., 63.0.3239.84 and above stable and Beta(m64) releases.

This crash is due to third party module "module_lifetime.dll(Avast)".

Few data points :
1. crash is distributed across Windows versions of which Windows 10 has highest crash rate.
2. Chromecrash dashboard reports "empty AV" 
3. module_lifetime.dll version is 0.0.0.0 

Please find details here : https://goto.google.com/tcckf

Note : Logged this issue since the crash rate 

Just to update, more than 11000 instances of this crash is observed so far on the stable build# 63.0.3239.132. Below link gives in detail for the number of instances in which the crash is occurring on respective builds:

https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27Third%20party%20-%20module_lifetime.dll%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#productversion:1000

Looping stability sheriff as well so that issue gets addressed.

Thanks.!

It looks like there is some sort of incompatibility with Avast software.  It results in Chrome crashing during shutdown. I sent an email to chrome-stability@google.com for advice.

I'll reach out to Avast.

This is a shutdown crash. Analysis from crash shows clear spike for AVG (30x spike) and Avast (14x spike):

http://shortn/_2WwXNYkO8X

I have reached out to contacts in Avast and am awaiting their response.

Removing from stability sheriffing queue because wfh@ is already looking at it.

Avast have replied and state:

"unfortunately, we have not been able to reproduce it ourselves for now, so we decided to disable this functionality temporary on x64 builds. It will be release in upcoming days."

We will continue to monitor stability over the next few days.

This appears to be an interaction between both AVG and Avast installed on the same machine, as for almost all (99.9%) of the reports that contain a system profile, both AVG and Avast is running.

The bug/crash seems to happen when there is a version mismatch between AVG and Avast e.g.

crash/444b16838109ee62:

Avast: 17.9.3761.0
AVG: 17.7.3660.0

crash/e8f9ae1268cf33f5:

Avast: 17.9.3761.0
AVG: 17.8.3705.0

I've been so far unable to find an old version of AVG to install to test this theory.

Avast have been made aware of this issue and are working on a fix.

Response from Avast: "we have analyzed the scenario with two DLLs loaded (one for AVAST brand and another one for AVG brand) and I can confirm the bug in the products, which leads to this originally unwanted behavior. Fortunately, it’s again already fixed in version 17.9., so it should disappear when people updates both products."

It seems Avast pushed a fix on Friday and this seems to have fixed the crashes, I now see crash rate returning to normal levels. Grateful to Avast for their quick response on this.