Using the provided regression range assigning to the possible suspect as per the change made for the file, “shared_worker_service_impl.cc”
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/7d01ede14b4669ab50cdf57a3625410d21bc15ca
@darin  -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thanks!

ClusterFuzz has detected this issue as fixed in range 507223:507276.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  filter in shared_worker_service_impl.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=500732:500783
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=507223:507276

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

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

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