This bug has been reported as M51 Stable blocker and We're cutting M51 Stable RC early next week. Anything actionable here needs to be resolved before then. Thank you.

Note  : The spike is huge on Chrome 64 bit  Stable i.e.,  51.0.2704.63

Version comparison of 64 bit chrome renderer crashes on the latest stable(51.0.2704.63) from the last stable(50.0.2661.102)

https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20cpu.Architecture%3D%27amd64%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&compProp=product.Version&v1=51.0.2704.63&v2=50.0.2661.102

Crashes [Renderer hang] Not hung (hang detector issue) and [Out of Memory] cc::SoftwareImageDecodeController::DecodeImageInternal are the Top 2,3 renderer crashes with significant spike on latest stable 51.0.2704.63

Assigning for further investigation to Václav, who is sheriffing today.

Sorry, I am not sheriffing today!

Assigning the bug to today's stability sheriff (this time correctly).

To update more on the Comment#5 where test team did the version comparison and below are crash magic Signatures which are causing almost 11.78% of over all crash % on current Stable 51.0.2704.63 when compared to previous Stable and happening on 64 bit Chrome :

1. [Out of Memory] cc::SoftwareImageDecodeController::DecodeImageInternal - 6084 crashes of 3849
2. blink::Font::getFontMetrics                                            - 5106 crashes of 3791	
3. v8::internal::Heap::IteratePromotedObjectPointers                      - 821  crashes of 486
------------------------------------------------------------------------------------------------------------
Total                                                                     - 12011/105211(Overall crashes on 51.0.2704.63 Chrome64bit)


Note : These are new crashes on Chrome 64 bit on 51.0.2704.63 which didn't existed in previous stable i.e., 50.0.2661.75. Link below for the same :
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20cpu.Architecture%3D%27amd64%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&compProp=product.Version&v1=51.0.2704.63&v2=50.0.2661.75#magicsignature:40,-magicsignature2:30,-stablesignature:30

Hi vmpstr@,
  Can you please take a look at this? if this is an issue or not. Heard we are trying to decide if this is a stopper or not.

thanks
raman

https://codereview.chromium.org/1682803003

I don't think this is an issue. Please see the discussion on crbug.com/610863

The summary is that this is a new stack trace for an existing out of memory crashes (some classes have changed names over the versions). However, I believe that the crash is not new...

vmpstr@: is it ok to mark this as duplicate of 610863?