titzer @ could you please look into this.please feel free to re-assigned back if needed. thanks in advance !

ClusterFuzz has detected this issue as fixed in range 432166:432259.

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

Fuzzer: inferno_twister
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  v8::internal::VerifyPointersVisitor::VisitPointers
  v8::internal::StandardFrame::IterateCompiledFrame
  v8::internal::Isolate::Iterate
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_chrome&range=431596:431606
Fixed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_chrome&range=432166:432259

Minimized Testcase (2.74 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94MljButfFeAnmjLVL52kf0kPPnD45lOo2BLYVR8G8pKSRqfiSonOsBcjLseR0UkMFtO2rY0R7F9Sv4PUwfixXaoQPz5J7mE-Tp0bgT0-sJgUe0kT3rvu9N0trD2JgsAk-uOnKH0zf0rENEXuR6QXnBY9Fksg?testcase_id=5240324713873408

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.

mlippautz@, can you take a look and see if it is reasonable that your recent flag flip CL fixed this?

https://codereview.chromium.org/2498343002

Nope; the path needs to be triggered by chromium and we will only enable it there after the branch cut.

ClusterFuzz testcase is verified as fixed, closing issue.

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

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