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

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

This appears to be caused by ElementVisibilityObserver.

ElementVisibilityObserver looks related to IntersectionObserverer.

mlamouri@, could you have a chance to take a look?

Also +Blink>Editing because the test is using editing commands.

Assigning to skyostill@ to investigate the calling site first (EVO is used in different places so it's likely this is specific to this usage).

Hmm, is the bug here that we're not tracing the callback in the observer?

https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/intersection_observer/IntersectionObserver.cpp?rcl=b860ecad247794f36735be49900cb01fca27e5ee&l=52

Are base::Callbacks GC'd objects that need to be traced?

ClusterFuzz has detected this issue as fixed in range 566300:566302.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  BindRepeating<void
  BindRepeating<void
  blink::ElementVisibilityObserver::Start
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=512477:512486
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=566300:566302

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

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

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