ClusterFuzz has detected this issue as fixed in range 37241:37255.

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

Fuzzer: decoder_langfuzz
Job Type: linux_asan_chrome_v8_d8
Platform Id: linux

Crash Type: Stack-use-after-return READ 8
Crash Address: 0x7f12f201d650
Crash State:
  v8::internal::Runtime_LoadGlobalIC_Miss
  v8::internal::Invoke
  v8::internal::Execution::Call
  
Regressed: V8: r37168:37191
Fixed: V8: r37241:37255

Minimized Testcase (7.51 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94Bf2JZprE3bEgWXzPcnSuyyBl7-3dn1sFAPgJ6wviYcYeUaPo1DQyLbz8g5nN0Ka56b1d2u0Dpb7mldWcW_ZcJKCyjmcL06lRR1YAeOcjdXryw9IOWVSctyEEVF2bPtYowoTb0EJide3tfJSGsnSeMqdlQ2g?testcase_id=4812393272311808

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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

Adding Merge-Triage label for tracking purposes.

Once your fix had sufficient bake time (on canary, dev as appropriate), please nominate your fix for merge by adding the Merge-Request-XX label, where XX is the Chrome milestone.

When your merge is approved by the release manager, please start merging with higher milestone label first. Make sure to re-request merge for every milestone in the label list. You can get branch information on omahaproxy.appspot.com.

- Your friendly ClusterFuzz

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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