Predator and CL did not provide any possible suspects.
Using Code Search for the file, "builtins-console.cc" assigning to the concern owner using GIT Blame.

Suspecting Commit#
https://chromium.googlesource.com/v8/v8.git/+/701d79d08ad4cb8fb6c61d49a5fb2a4862f29d9e

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

ClusterFuzz has detected this issue as fixed in range 485894:485942.

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

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_ConsoleTimelineEnd
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=471987:472013
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=485894:485942

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


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.