New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 698390 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

There is a 10% spike in Renderer crashes on Windows Chrome M57 compared to M56

Project Member Reported by pbomm...@chromium.org, Mar 3 2017

Issue description

There is a 10% increase in number of Renderer crashes when compared to M56(56.0.2924.67) to M57(57.0.2987.74), Please find the details from below url and the crashes which are causing below : 


Comparision URL :
https://goto.google.com/xynqs 

Crashes which caused the spike                 56.0.2924.67             57.0.2987.74      Bug                 Spiked %                
------------------------------------------------------------------------------------------------------------------------
Corrupted report                               0.01%	5		7.74%	3555     crbug.com/696258      7.73%(No Resolution yet)
base::partitionOutOfMemory                        0%	0		6.02%	2766	 crbug.com/676740      6.02%(OOM)
No files to process                            0.65%	246		2.11%	969	 crbug.com/680342      1.46%
ChromeMain                                        0%	0		1.72%	788	 crbug.com/683848      1.72%(Third party)
blink::anyAttributeMatches                        0%	0		1.30%	598	 crbug.com/672391      1.30%(Wontfix)
blink::FontFaceCache::get                         0%	0		1.24%	569	  crbug.com/531399       1.24%(Wontfix)
TargetNtCreateFile                             0.01%	3		1.43%	656	 crbug.com/681086      1.42%


rmargold@chromium.org and wfh@ apologize for another bug given we have bugs for the respective crashes and they are marked as no stable blockers but those bugs show that we are causing overall spikes and want to confirm one lasttime before we go M57 prestable next week.


Note : I haven't included any longstanding issues as part of the comparision, Also I picked 1 week old M57(57.0.2987.74) for comparison since the latest version of Beta is too early to compare.
 
Thank you Prudhvi.

M57 stable launch is coming soon (RC cut on Monday, 03/06), please take a look ASAP and let us know if this is a potential blocker for M57 Stable promotion.

Comment 2 by wfh@chromium.org, Mar 3 2017

Cc: palmer@chromium.org
A few comments:

"ChromeMain" crash 1.72% is App Container related due to a fieldtrial only on canary/dev/beta channel so shouldn't be promoted to stable.

"base::PartitionOutOfMemory" looks 'new' because that code moved around recently, but I expect it's just a different signature for the same OOMs +palmer
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 6 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

Comment 4 by wfh@chromium.org, Mar 6 2018

Status: WontFix (was: Untriaged)

Sign in to add a comment