Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/35eb246ef089371ad11b6bd24c384004eea274e3 (Restructure VR asset component histogram names).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

This CL is only variable rename, string change, and histograms.xml update. This should not affect memory dereferencing.

Predator and CL could not provide any possible suspects.
Using the code search for the file, “connector.cc” assigning to concern owner from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/1f1f6b2a18c89d1340d023f2cdb15b2a5c91663e

@ben -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 522368:522379.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000018
Crash State:
  service_manager::Connector::BindConnectorIfNecessary
  service_manager::Connector::BindInterface
  void service_manager::Connector::BindInterface<ukm::mojom::UkmRecorderInterface>
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=521085:521097
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=522368:522379

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

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

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