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

Something somplicated going on, but this is a Release assert due to the inability to allocate an image, so most likely not a big deal. Dropping the priority.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/18fc5e473594ff6bb062183835a60257def9a627 ([SPv1] Always set a CompositorElementId on main graphics layers; use PaintLayer id.).

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

This is a deliberate release assert trying to allocate a bitmap that is too large. Working as intended.

ClusterFuzz has detected this issue as fixed in range 506552:506627.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900000001
Crash State:
  blink::PictureSnapshot::Replay
  blink::InspectorLayerTreeAgent::replaySnapshot
  blink::InspectorLayerTreeAgent::replaySnapshot
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=473072:473106
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=506552:506627

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

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.