Link to the Win and Mac canary(64.0.3279.0) browser crashes:
============================================================
Win: https://goto.google.com/bbfyk
Mac: https://goto.google.com/stchx 

Link to the Win and Mac canary(64.0.3278.0) browser crashes:
============================================================
Win: https://goto.google.com/geakt
Mac: https://goto.google.com/xhtmw

Top experiments running as per the above link on #64.0.3279.0:

Windows
==================================================================
1	e258b09e-3f4a17df	102.06%	4070 ChromeWinClang: Enabled	
2	6025934e-3f4a17df	101.83%	4061 ChromeChannelCanary: Enabled	
3	ed1d377-e1cc0f14	101.83%	4061 UMA-Uniformity-Trial-100-Percent: group_01	
4	7aa46da5-c946b150	101.83%	4061 SRTPromptFieldTrial: NewCleanerUIExperiment	
5	25fc488a-4d2fac87	101.71%	4056 SafeBrowsingAtRiskAccountFlagging: Enabled_Launch	
6	16e0dd70-3f4a17df	101.65%	4054 AutofillFieldMetadata: Enabled	
7	cac0a91c-388b6f1c	101.60%	4052 SettingsResetPrompt: EnableSettingsResetPrompt	
8	3ac60855-486e2a9c	101.48%	4047 UMA-Population-Restrict: normal	
9	f79cb77b-3f4a17df	101.35%	4042 PasswordGeneration: Enabled	
10	b1edbc38-cf4f6ead	101.30%	4040 DecoupleTranslateLanguage: Experiment

Mac
====================================================================
1	25fc488a-4d2fac87	101.06%	1718 SafeBrowsingAtRiskAccountFlagging: Enabled_Launch	
2	ed1d377-e1cc0f14	101.06%	1718 UMA-Uniformity-Trial-100-Percent: group_01	
3	6025934e-3f4a17df	101.06%	1718 ChromeChannelCanary: Enabled	
4	16e0dd70-3f4a17df	101.06%	1718 AutofillFieldMetadata: Enabled	
5	c559031-3d47f4f4	99.71%	1695 SyntheticDataReductionProxySetting: Disabled	
6	47e5d3db-3d47f4f4	98.59%	1676 DataCompressionProxyHoldback: Disabled	
7	8e3b2dc5-93702590	98.47%	1674 NoStatePrefetchRollout: NoStatePrefetchEnabled	
8	79616653-3f4a17df	98.47%	1674 EnableDialLocalDiscovery: Enabled	
9	34d450b1-f23d1dea	98.47%	1674 EnableCastDiscovery: Control	
10	5485fc4d-ca7d8d80	91.41%	1554 NativeCrxBindings: Default

> Searched in critique and didn't find any related experiments landed recently and aligning with the recent spike of these crashes.

Top components of crashes logged on #64.0.3279.0:

Windows
=====================================================
1	src/content/public/browser	        71.21%	2840	
2	src/chrome/browser/resource_coordinator	14.29%	570	
3	src/mojo/edk/system	                 2.66%	106	
4	empty	                                 1.00%	40	
5	src/mojo/edk/system/ports	         0.90%	36	
6	src/base/message_loop	                 0.83%	33	
7	src/base/task_scheduler	                 0.65%	26	
8	src/base	                         0.65%	26	
9	src/net/base	                         0.45%	18	
10	src/mojo/public/cpp/bindings/lib	 0.38%	15

Mac
=======================================================
1	src/third_party/llvm-build/release+asserts/include/c++/v1	29.94%	509	
2	src/chrome/browser/resource_coordinator	                        11.47%	195	
3	empty	                                                         9.76%	166	
4	src/base/message_loop	                                         7.41%	126	
5	src/mojo/edk/system	                                         5.65%	96	
6	src/base/third_party/libevent	                                 5.59%	95	
7	src/base	                                                 4.12%	70	
8	src/content/browser	                                         2.18%	37	
9	src/base/memory	                                                 2.06%	35	
10	src/mojo/edk/system/ports	                                 1.65%	28	

> For 1 & 2 components on Windows and Mac, suspected experiment is already being reverted in Issue 789084.
> For 3 & 5 components on Windows and 5 & 10 components on Mac, from the regression range(https://chromium.googlesource.com/chromium/src/+log/64.0.3278.0..64.0.3279.0?pretty=fuller&n=10000):

   https://chromium-review.googlesource.com/c/chromium/src/+/792255 is the only CL touching mojo/edk/system. Only reason this looks unrelated is, this didn't show any similar spike when the CL first landed in  Issue 753541 .

> Some of the mojo related magic signatures spiked on the latest Win and Mac canary(64.0.3279.0): mojo::edk::Channel::OnReadComplete, mojo::edk::WatcherDispatcher::NotifyHandleState, 	mojo::edk::NodeChannel::OnChannelMessage, mojo::edk::NodeController::PortStatusChanged, mojo::edk::ports::UserMessageEvent::Deserialize, mojo::FilterChain::Accept, mojo::edk::ports::Node::GetPort.

> There are no such mojo/edk/system/ and  base/message_loop related top components seen on the previous Windows and Mac canary: 64.0.3278.0.

Suspecting the recent spike either could be related to the same experiment as in Issue 789084 or caused due to CL reland in  Issue 753541 .Looping Devs from the related CLs and stability sheriff for their inputs and further investigation of these recent spike. 


Note: M-64 will be branched tomorrow on 11/30.