Alongpower85@gmail.com

ClusterFuzz has detected this issue as fixed in range 482197:482214.

Detailed report: https://clusterfuzz.com/testcase?key=5435663645409280

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !interface_object.IsEmpty() in V8PerContextData.cpp
  blink::V8PerContextData::CreateWrapperFromCacheSlowCase
  blink::V8PerContextData::CreateWrapperFromCache
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=481516:481566
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=482197:482214

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5435663645409280


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.

Bisecting by hand, V8's roll-in (https://codereview.chromium.org/2954483002) seems to be the trigger.
I think it fails in 'try { ... } catch() { ... }', and the CHECK() failure in #0 is not the critical reason.

I'm not sure if it is really fixed or flaky. Set P2 for a while.

ClusterFuzz testcase 5435663645409280 is verified as fixed, so closing issue.

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