Unable to find actual suspect through code search and also from the provided CL under regression range, hence adding appropriate label and leaving it as untriaged for further updates.

Thanks!

Looks like ukm_recorder_ may be leaking on Document. Not sure if this should really matter assuming it's only a renderer shutdown leak?

+CC holte as the last person to change blink::Document::UkmRecorder().

ClusterFuzz has detected this issue as fixed in range 537181:537198.

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

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

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  mojo::internal::InterfacePtrState<ukm::mojom::UkmRecorderInterface>::ConfigurePr
  instance
  get
  
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=537181:537198

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

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

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

Since the ukm_recorder_ is held in a unique_ptr, is this a case where the Document object itself is leaked?

 Issue 813409  has been merged into this issue.

Re-opening this because it's appearing again (see  issue 813409 ).

I agree with #5 that it looks like a Document leak.

 Issue 814980  has been merged into this issue.

+hajimehoshi, since one of the reasons that UKM recorder exists on Document is to help identify causes of document leaks per https://bugs.chromium.org/p/chromium/issues/detail?id=757374

This crash occurs very frequently on linux platform and is likely preventing the fuzzer ifratric-browserfuzzer-v3 from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.

Friendly ping to get an update on this issue as it is marked as beta blocker.

Thanks..!

A friendly reminder that M67 branch is coming soon on 04/12! Your bug is labelled as Beta ReleaseBlock, pls make sure to land the fix ASAP to trunk. This way we branch M67 from a high quality trunk. Thank you.

 Issue 821363  has been merged into this issue.

This is not a Mojo bug, so removing that component. The report implies that a UkmRecorderInterface endpoint is leaking. See comments #7 and #9 for more context.

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/+/62d0093b891fa483449513db827aee7b36760e0c (MD Extensions: eliminate lags when clicking between errors in the error console.).

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.

A friendly reminder that M67 branch is coming soon on 04/12! Your bug is labelled as Beta ReleaseBlock, pls make sure to land the fix ASAP to trunk. This way we branch M67 from a high quality trunk. Thank you.

Gentle ping to get an update on this issue as it is marked as beta blocker fro M67 & M67 branch is coming soon on 04/12

Thanks..!

I don't know how to fix the Document leak here, but we could potentially avoid leaking the UkmRecorderInterface object around when that happens, either by:
* By not holding onto the UkmRecorderInterface and creating new ones from connector as needed.
* By keeping a single shared UkmRecorderInterface somewhere (maybe Platform?)

Given that other objects must be being leaked here I'm not sure what severity of leaking UkmRecorderInterface is.

A friendly reminder that M67 branch is tomorrow, Thursday 04/12! Your bug is labelled as Beta ReleaseBlock, pls make sure to land the fix ASAP to trunk. This way we branch M67 from a high quality trunk. Thank you.

Removing ReleaseBlock-Beta since it doesn't seem like this is severe enough to warrant it.

My understanding is that:
* This occurs when a Document leaks
* Document leaks in general are not a new issue.
* This extra object being leaked is only adding a couple bytes to that existing leak.

+yuzus, keishi who are looking at document leaks

Please assign this to a more applicable owner.

 Issue 835022  has been merged into this issue.

This issue has been fixed.