Users experienced this crash on the following builds:

Win Beta 54.0.2840.59 -  5.15 CPM, 219 reports, 214 clients (signature sandbox::SharedMemIPCServer::ThreadPingEventReady)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

This is listed as #2 browser crash in latest Stable reports - 54.0.2840.59 ,79.75% with 1500+ unique clients.

Almost all the reports have malware loaded - icaendpoint.dll,looping would to Stability sheriff for confirmation.

Details  below.
==============
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%27sandbox%3A%3ASharedMemIPCServer%3A%3AThreadPingEventReady%27%20AND%20product.Version%3D%2754.0.2840.59%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,3rdparty,oncrashedthread,oncrashedthreadv,isinfected

So far seeing 2087 instances from 1954 different client ids.

Link to the list fo builds
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20product.version%3D%2754.0.2840.59%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27sandbox%3A%3ASharedMemIPCServer%3A%3AThreadPingEventReady%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D

54.0.2840.59	83.78%	2087	

Adding stable blocker as seeing spike on M54.Please feel free to remove if not required.

Re #2: This doesn't look like malware, but it does seem that some third-party dll is related to the crash.

+wfh, can you take a look?

this appears to be a very old version of Citrix from 2012, having a bad interaction with Chrome 54.

Since we're already in Stable, I don't think this meets the bar for RBS.

Will - are you looking into what the interaction is? Should this be on sheriff queue?

So far seeing 5189 instances from 4638 different client ids on current beta 54.0.2840.59	

55.0.2883.11	0.07%	4	
55.0.2883.9	0.02%	1	
55.0.2882.4	0.04%	2	
55.0.2873.0	0.05%	3	
55.0.2871.0	0.02%	1	
55.0.2870.0	0.02%	1	
55.0.2868.3	0.07%	4	
55.0.2859.0	0.05%	3	
55.0.2847.0	0.02%	1	
54.0.2840.59	92.84%	5189	Beta
54.0.2840.50	0.11%	6	
54.0.2840.27	0.11%	6	

Experiencing this on Server 2008 R2 Citrix servers, Chrome V54.0.2840.71, even on the latest long-term release version of Citrix XenDesktop (7.6.300).  The app fails when running in a seamless window (works under a published desktop).  The crash does NOT occur on a Server 2012 R2 Citrix server; runs as expected.

This occurs with both 32-bit and 64-bit enterprise releases.

the '--no-sandbox' command switch will allow v54 to launch on the Server 2008 R2 servers, but with a warning message.

cgoffrie, are you running on production systems with --no-sandbox?  I'm not sure that would be a great idea.

This is #1 crasher for Win32.  Any updates, Will?

ligimole@, note that infection fraction is only 19%.

https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20product.Version%3D%2754.0.2840.71%27%20AND%20cpu.Architecture%3D%27x86%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#-samplereports:5,isinfected

To be more precise, this is #1 crasher for Win32 browser on the current stable version 54.0.2840.71.

I am not running on production system using --no-sandbox.  We are keeping our prod deployment at v51 Enterprise until this bug is worked out.  Just reporting all the results of my testing. :)

Just to update:

This is top #2 browser crash for Windows on the current stable version 54.0.2840.71 with 12835 instances from 10760 unique client Ids

This could be same root cause as  issue 659026 

Adding Release block label, since the instances in the stable are pretty high. Next stable is planned to be pushed soon. 

wfh@: Can you please take a look into it. Please undo or remove blocker label if not the case.

Instances on Current Stable 54.0.2840.71 - 19680:
=================================================
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%27sandbox%3A%3ASharedMemIPCServer%3A%3AThreadPingEventReady%27%20AND%20product.Version%3D%2754.0.2840.71%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D

Note: So far no instances are reported on market beta 55.0.2883.28.


Thanks.!

Looks similar to  issue 659026  which is already fixed.
Keeping RB label for tracking purpose until the next stable update scheduled next week.