Predator and CL could not provide any possible suspects.

Using Code Search for the file, "mojo_ukm_recorder.cc" and observed there was some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/e830e7e38a287e5312e21db9f5aeb080d7bc30c8%5E%21/services/metrics/public/cpp/mojo_ukm_recorder.cc

holte@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 602872:602890.

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

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

Crash Type: Direct-leak
Crash Address: 
Crash State:
  ukm::MojoUkmRecorder::Create
  blink::Document::UkmRecorder
  blink::Document::Shutdown
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=209699:209703
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=602872:602890

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

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.