Unable to find actual suspect through code search and also from the provided CL, hence marking it as untriaged.

Note: Observing some recent changes for the below file 'mojo_async_resource_handler.cc', so cc'ing to @jam for more updates on this issue.

https://chromium.googlesource.com/chromium/src/+/462480368214f523f93f9e4a1a99a272a3159061

Thanks!

ClusterFuzz has detected this issue as fixed in range 539913:539918.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  ((data_.proc_self_maps.mmaped_size)) > ((0)) (0, 0)
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=508795:508862
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=539913:539918

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

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

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