Looks like another runtime assert failure. mbarbella, is this a result of your triggers?

Yeah, this is the same problem mentioned in issue 595257. We should no longer be detecting these for langfuzz and should start seeing fixed reports soon. I'll close after confirming.

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

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

Fuzzer: decoder_langfuzz
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  size <= Page::kMaxRegularHeapObjectSize in src/runtime/runtime-internal.cc
  
Regressed: V8: r34400:34401

Minimized Testcase (9.23 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97NYSPShekS78CAqEMLj2CI42HJ918cknennYFIu-nuTiQoVtb0yeGGZUe94gFismAKh_d8tOqSsfjtI4B7-7ppo5wFcgwC1j2DU7AcgG_0BStioXoA0FxV_4deYZyZqrtn836rKP3FqpuR6gPsGnZcEKFTkQ

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot