This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Same as  Issue 729490 , which has the same stack but a different regression range?

I checked the code and this is crashing on the same ValueOrDie() call.

ClusterFuzz has detected this issue as fixed in range 491722:491739.

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

Fuzzer: miaubiz_svg_fuzzer
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Illegal-instruction
Crash Address: 0x29426580
Crash State:
  gfx::Size::GetArea
  cc::ResourcePool::TryAcquireResourceForPartialRaster
  cc::TileManager::CreateRasterTask
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=456301:456305
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=491722:491739

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6117694419238912


See https://github.com/google/clusterfuzz-tools for more information.

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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