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 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/+/b346beb380ac646762daa5c561d088afc12f6877 (oop: Add transfer cache deserialization fuzzer).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/b346beb380ac646762daa5c561d088afc12f6877 (oop: Add transfer cache deserialization fuzzer).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

ClusterFuzz has detected this issue as fixed in range 541532:541550.

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

Fuzzer: libFuzzer_transfer_cache_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  SkImage::makeColorSpace
  cc::ServiceImageTransferCacheEntry::Deserialize
  transfer_cache_fuzzer.cc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=541281:541292
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=541532:541550

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 5928507558068224 is verified as fixed, so closing issue as verified.

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