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

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

Hmm.  No suspect CL in range.

dalecurtis@ - You're an owner here and seem to have some familiarity with this code.  Could you take a look or re-assign as appropriate? Thanks!

Probably this is just ClusterFuzz getting hold of internals.* methods it shouldn't be again. I forget the bug we dupe these into, but will double check.

Correct. I did reach out to the team and there was no clear answer. I think we should remove setMediaElementNetworkState. It's used in two tests for a total of three times. We already got much more than three clusterfuzz bugs because of it :) 

ClusterFuzz has detected this issue as fixed in range 557279:557285.

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

Fuzzer: inferno_layout_test_fuzzer
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x127719f87900
Crash State:
  Bad-cast to blink::WebAudioSourceProvider from invalid vptr
  blink::HTMLMediaElement::AudioSourceProviderImpl::Wrap
  blink::HTMLMediaElement::StartPlayerLoad
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=527199:527221
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=557279:557285

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

Additional requirements: Requires HTTP

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