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/+/3a80a7da38d984fde137c6a1a2848bac4585a9c6 (Disable Flaky SitePerProcessHitTestDataGenerationBrowserTest.ClippedOOPIFFastPath).

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.

My change only disabled a test.

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

bnc@, could you take a look if it is related to your change in https://chromium.googlesource.com/chromium/src/+/f7f0831aba6a8afced482a5ba4be3851c024fbe9

ClusterFuzz has detected this issue as fixed in range 582465:582466.

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

Fuzzer: inferno_twister
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  storage::DatabaseTracker::UpdateOpenDatabaseInfoAndNotify
  storage::DatabaseTracker::DatabaseClosed
  content::WebDatabaseHostImpl::Closed
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=581163:581164
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=582465:582466

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

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.

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

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

Theoretically it could have been related to my change (though I do not quite see how), but Clusterfuzz thinks it's fixed now.  I think this must have been a false alarm.

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