Find it did not provide any possible suspect, assigning to the concern owner from the regressed range,
https://chromium.googlesource.com/chromium/src/+log/a241953aa9d0ecd5375771e634f8638e004a9961..f29b3424711e7a435c904705e9e5865603a67c09?pretty=fuller

Suspecting the commit --
https://chromium.googlesource.com/chromium/src/+/98bea5472ae292ed699c3ecdb7512cee1de5904a

@cwallez -- Could you please look into the issue, kindly re-assign if this is not related to your change.
Thank You.

The problem is that ANGLE inserts initialization code for uniform one by one. This is the expected behavior.

If the fuzzer keeps finding hangs or OOMs like this we will consider adding an arbitrary limit to make it happy.

ClusterFuzz has detected this issue as fixed in range 438777:438804.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5983758244380672

Fuzzer: libfuzzer_angle_translator_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory
Crash Address: 
Crash State:
  angle_translator_fuzzer
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=420346:420472
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=438777:438804

Minimized Testcase (0.92 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95BhDZioWoxYgKokJGoPvog2xodSFvOzECw_TWNk944j8RQZSt_5QCDMU8aT8Rd0jG6AoTW0hfTkgVJ1HuyGB7pC63kpC_ZOS3XSuAXVJBny8s8PXmAL_Zf_o2IJc5BL2sOt3IJOhJQ89mlEa75p5PddLVMgg?testcase_id=5983758244380672

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.