Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "grid_track_sizing_algorithm.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/75d24bd94da41caf2a6a0061b3ae528a7528a79e

jfernandez@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Umm, I cannot reproduce it in today's ToT (linux) 

It's not reproducible in the following versions either:

 * Google Chrome	69.0.3472.3 (Official Build) dev (64-bit)
 * Google Chrome	68.0.3440.42 (Official Build) beta (64-bit)

I tried to build at the specific suspicious commit and I'm still unable to reproduce the issue. In my opinion, it's not the root cause of the issue. 

I think I managed to reproduce the issue. 

I think I managed to reproduce the issue. 

Hi, I can reproduce the issue even in versions earlier (r564745) than the one the suspected CL belongs to (r564950), so definitively it's not the root cause of this bug.

Non-security numeric overflow bugs are considered won't fix.

ClusterFuzz testcase 5194601586229248 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.