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/+/a443faa044b0e1472b36d35aaf425ae0ee6b2ac5 (Element capture: Do not check cross origin for elements with srcObject.).

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

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

r506465 reverts the culprit CL. More details in  bug 771388 .

Making it public, since this was just a recent regression.

ClusterFuzz has detected this issue as fixed in range 507089:507129.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Heap-use-after-free READ 1
Crash Address: 0x60300009b785
Crash State:
  base::internal::WeakReference::is_valid
  content::HtmlVideoElementCapturerSource::sendNewFrame
  base::debug::TaskAnnotator::RunTask
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=506452:506506
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=507089:507129

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

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

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

Both regressed and fixed in M63, removing ReleaseBlock-Stable