Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.

geofflang@, Just wondering would it be caused by this change (https://chromium.googlesource.com/chromium/src/+/3a1cd2993891a85b18bd024993e9c1930f21311c) ?

Thank you!

manoranjanr@, there is no chance this CL caused this failure.  I'm not sure who could own this bug.

ClusterFuzz has detected this issue as fixed in range 510178:510268.

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

Fuzzer: mbarbella_webcomponents
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in aligned_memory.cc
  c:\clusterfuzz\slave-bot\builds\chromium-browser-asan_win32-release_a15986b6468d
  c:\clusterfuzz\slave-bot\builds\chromium-browser-asan_win32-release_a15986b6468d
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=480859:480871
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=510178:510268

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

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

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