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/+/31c3e8642532f753ab688445c7093012dba3f8f1 ([vr] Add not-web-exposed media feature for immersive mode.).

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.

Needs
	immersive_mode(false),

inside the MediaValuesCached::MediaValuesCachedData::MediaValuesCachedData() member initialization list?

The offending change has already been reverted.

CL: https://chromium-review.googlesource.com/c/chromium/src/+/905062

Proper fix is up here (https://chromium-review.googlesource.com/c/chromium/src/+/905782), though I'm currently having troubles reproducing. clusterfuzz is telling me that vollick@google.com doesn't have access to the test case.

Looks like cc'ing vollick@google.com fixed my repro issue and I think that the posted fix (which makes the change elawrence@ suggested) addresses the problem.

ClusterFuzz has detected this issue as fixed in range 534724:534740.

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

Fuzzer: libFuzzer_html_preload_scanner_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  blink::MediaAttributeMatches
  void blink::TokenPreloadScanner::StartTagScanner::ProcessLinkAttribute<WTF::Atom
  blink::HTMLPreloadScanner::Scan
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=534492:534497
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=534724:534740

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

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 6231504766894080 is verified as fixed, so closing issue as verified.

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

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