mstarzinger@ could you please look into this, please re- assign back if it not your change. thanks in advance

ClusterFuzz has detected this issue as fixed in range 405563:405613.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4820397073891328

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  args[0]->IsString() in runtime-strings.cc
  backtrace
  __tsan::CallUserSignalHandler
  rtl_sigaction
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=405163:405185
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=405563:405613

Minimized Testcase (12.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96aU5HojPTcXFVrSWa2JzQHdOaKQv-uUQshvtEu0pWjRC32wlHuL8HQ8lnnKHiyW0xvxl3p80RON-21ykupsOtUAAeZpkV_cBLp-_zB4wlKc5iDsnKCfjHhPQP8F55-W4m3Q9x9adIXWBxLn0RvgTOSMw_XCg?testcase_id=4820397073891328

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.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot