This looks more like a bindings issue judging by the stack-trace. Seen as  issue 761048  and  issue 764697  recently as well.

Predator and CL could not provide any possible suspects.
Using the code search for the file, “V8PerContextData.cpp” assigning to concern owner from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/c9fb57013ff1b06ebae362c1942ff9a1868268f8
@yukishiino -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Testcase 5599696998629376 is a top crash on ClusterFuzz for windows platform. Please prioritize fixing this crash.

Marking this crash as a Beta release blocker.

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

M-63 will be branched in next few days, and would be good to have all the Beta blockers resolved before branch point.

yukishiino@: Could you please take a look at this issue marked as Beta blocker for M-63.

Let me remove ReleaseBlock-Beta since this is not a new issue nor we've not made a change on this point for a while.  This has been a known issue which we cannot fix immediately.

ClusterFuzz has detected this issue as fixed in range 509712:509715.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !interface_object.IsEmpty() in V8PerContextData.cpp
  blink::V8PerContextData::CreateWrapperFromCacheSlowCase
  blink::V8DOMWrapper::CreateWrapper
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=504624:504629
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=509712:509715

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

See https://github.com/google/clusterfuzz-tools 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 5599696998629376 is verified as fixed, so closing issue as verified.

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