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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/fdacdc9f7bd8e4b0cf23b192e959c2350f693e7c (Reland images: Move animation of images to cc.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

This is a dupe of 775558 which has already been fixed. The current range on the bot is 503872:503913 while the fix landed on r512695, so should be detected as fixed once it gets there. The feature that introduces this is behind a flag, it shouldn't have an impact on any official release. The reason why the bot caught it is because it has been enabled for field trial testing so the bots run with the flag enabled.

ClusterFuzz has detected this issue as fixed in range 512693:512729.

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

Fuzzer: inferno_webbot
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Unknown exception
Crash Address: 0x0defb964
Crash State:
  blink::DecodingImageGenerator::GetContentIdForFrame
  cc::PaintImage::GetKeyForFrame
  cc::ImageDecodeCacheKey::FromDrawImage
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=503872:503913
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=512693:512729

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

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