Suspected CL is
https://chromium.googlesource.com/v8/v8/+/8ee581af4b6de5ac4beda973461fef2b4e105339%5E%21/src/ast/scopes.cc

marja@, could you please take a look and help us to find correct owner if it is not related your changes.

ClusterFuzz has detected this issue as fixed in range 41227:41228.

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

Fuzzer: decoder_langfuzz
Job Type: linux_asan_d8_v8_arm_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  is_block_scope() in scopes.cc
  
Regressed: V8: r41221:41222
Fixed: V8: r41227:41228

Minimized Testcase (6.09 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95AxDVJZZGXPgfzjdchOpP3oUWSbS524bSptx3oS75WVjdcHTj2kedpCy98B54ULMXy5EC4QYvgmegQe4BuIIZL0VJCFOFtVJBky4DQYSg6L89RrsaEEj9xnWGBXxM-abNZMyvm5_CHtTvcvLjkQVwtqFOu9w?testcase_id=6697925515411456

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.

Re comment 1, why would suspect that CL (V8 revision 39233) when the report states that the regression range in the report is 41221:41222?

This is the guilty one:

commit f385268d11d6da9508e481202b39f75f4b56afdd
Author: neis <neis@chromium.org>
Date:   Wed Nov 23 05:25:04 2016 -0800

    [parser] Fix scopes in rewriting of for-of and destructuring assignments.
    
    The catch scopes were created with the wrong parent scope.
    
    R=littledan@chromium.org
    BUG= v8:5648 
    
    Review-Url: https://codereview.chromium.org/2520883002
    Cr-Commit-Position: refs/heads/master@{#41222}


Revision 41228 is the revert (and clusterfuzz has detected the problem fixed).