Assigning to https://code.google.com/p/chromium/codesearch#chromium/src/third_party/webrtc/modules/desktop_capture/OWNERS&sq=package:chromium&type=cs

owners for further investigation.

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6712040239923200

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 4
Crash Address: 0x7f332aa3ff70
Crash State:
  libyuv::ScaleARGB
  ARGBScale
  content::DesktopCaptureDevice::Core::OnCaptureCompleted
  

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94R6d2N4y7NZOtIiGbixMmwpZqniLtLjH-YLwxQpvs1LTnp2aB8uZYSbLCYTuU0IPY2PGhbp-dvbKIeQJzb7z-SJvaUtdAOjkhkIa2yzPoj457O5ugM4fxvnjBBBi9jM3_nq9OdQ_PnmR9dZHXUcXAjMIv20Oc3i1zwxMSqKz91Gu7hzVM


Additional requirements: Requires HTTP

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Abhishek, Marty, the race stack doesn't include libyuv::ScaleARGB, why is it in the summary?

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot