Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: svillar
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/70a22ecc29b1197a37f860b88fd0dd56b2e9cd2d
Time: Tue Nov 22 15:47:06 2016
File LayoutGrid.cpp is changed in this cl (and is part of stack frame #1, "blink::LayoutGrid::computeAutoRepeatTracksCount"; frame #2, "blink::LayoutGrid::placeItemsOnGrid"; frame #3, "blink::LayoutGrid::layoutBlock")
Minimum distance from crash line to modified line: 24. (file: LayoutGrid.cpp, crashed on: 538, modified: 514). 

Author: svillar
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/2c3a3d0ac5362c2d07040a821bb3a22f701d58b6
Time: Tue Nov 22 18:36:12 2016
File LayoutGrid.cpp is changed in this cl (and is part of stack frame #1, "blink::LayoutGrid::computeAutoRepeatTracksCount"; frame #2, "blink::LayoutGrid::placeItemsOnGrid"; frame #3, "blink::LayoutGrid::layoutBlock")
Minimum distance from crash line to modified line: 26. (file: LayoutGrid.cpp, crashed on: 215, modified: 189).

@svillar -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 455091:455392.

Detailed report: https://clusterfuzz.com/testcase?key=6450077821566976

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: Floating-point-exception
Crash Address: 
Crash State:
  blink::LayoutGrid::computeAutoRepeatTracksCount
  blink::LayoutGrid::placeItemsOnGrid
  blink::LayoutGrid::layoutBlock
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=433807:434033
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=455091:455392

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97synBH4HQ8IYzCUbK5YaIHdTpjVHXBKjIQArpVfCVhkmrSfUFkgqVdiC3vd7IJTk7NWD2CqyVz7qnGnfT6I7fIe1c9SDxSuZb_mJmM6Kd29oRKpnTL5cxVNu45X7sG_QG_JEzhN3JDuX30EoNwRJYhrE7uwy84Kvh1QccgEMq8FT555s7VzK-NXrsQphj5ehHRUbKZVX89TIhGIRoFpyIngGw6CPtvhXlCXRu89_274jw_Js1_Qqudai5cIRmkWdYfftugCFBzOh2UmWZEFuqVijGOFh4Dr2_TViCZAzKpnufVLP607QlW5M2XldRroBVDKsjOvdRJuUYMXgoUegEgxzY3KUYvjrkvngjhN4Qk6M9N184?testcase_id=6450077821566976


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6450077821566976 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.