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/+/780534183c285fc2f43821b905c5191694b873a2 ([Mac] Support #MacRTL feature in MacViews dialogs).

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.

Pretty sure this change is unrelated, not seeing anything in the stack trace related to the change, or anything in the change that could conceivably leak.

ClusterFuzz has detected this issue as fixed in range 543680:543683.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  base::CreateThread
  CreateNonJoinableWithPriority
  base::PlatformThread::CreateNonJoinable
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=522777:522778
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=543680:543683

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

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

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