Adithya, mind having a look?

It looks like calling the constructor for Event in V8 results in a stack overflow (which is detected here when the USE_SIMULATOR flag is true: https://chromium.googlesource.com/v8/v8.git/+/c7d2d2169f1f4d6d3f1e958a9102a4beb8bd4a95/src/execution.cc#70); so v8::Function::NewInstance returns an empty wrapper, which is causing the null deref. 

This is another case of Blink not handling exceptions thrown in V8, and I'm not sure if there's a simple way to fix this. 

Do you have a reproducible JS code?  I'm curious why we hit a stack overflow.

ClusterFuzz has detected this issue as fixed in range 479657:479707.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x00000000
Crash State:
  v8::internal::GlobalHandles::MakeWeak
  v8::V8::MakeWeak
  blink::ScriptWrappable::SetWrapper
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=479657:479707

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


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 4598363571093504 is verified as fixed, so closing issue.

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