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/+/9779e9515ba716e5ed490c3ffce69d8f13eba521 (Add TSan suppression for latest debian release.).

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.

I am not the owner for this. Fixing owner.

This seems to be the duplicate of the  issue 808164 . Apparently the patch did not fix all the lock-order-inversion issues.

ClusterFuzz has detected this issue as fixed in range 553016:553017.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Lock-order-inversion
Crash Address: 
Crash State:
  blink::MediaElementAudioSourceHandler::SetFormat
  blink::MediaElementAudioSourceNode::SetFormat
  blink::HTMLMediaElement::AudioClientImpl::SetFormat
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=526533:526534
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=553016:553017

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

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.