Predator and CL did not provide any possible suspects.
Using Code Search for the file, "builtins-console.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/v8/v8.git/+/54271c21e2860273abd6018c398b04f672ef2615

@kozyatinskiy -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Issue 725410 has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 474410:474439.

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

Fuzzer: v8_builtins_generator
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !isolate->has_scheduled_exception() in builtins-console.cc
  gin::PrintStackTrace
  v8::internal::Builtin_Impl_ConsoleTimeStamp
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=470579:470648
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=474410:474439

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


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

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