Unable to find the possible suspect from find it and CL.
Using Code Search for the file, "ScriptWrappableVisitor.cpp", assigning to the concern owner --

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

Thanks, taking a look!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ca07ee393934e403d0bb2e0d8790d8edbbe3df96

commit ca07ee393934e403d0bb2e0d8790d8edbbe3df96
Author: mlippautz <mlippautz@chromium.org>
Date: Mon Nov 28 12:07:26 2016

[wrapper-tracing] Avoid GC during PostMessageTimer construction

BUG= chromium:668742 ,chromium:668059, chromium:668060

Review-Url: https://codereview.chromium.org/2529353002
Cr-Commit-Position: refs/heads/master@{#434638}

[modify] https://crrev.com/ca07ee393934e403d0bb2e0d8790d8edbbe3df96/third_party/WebKit/Source/core/frame/LocalDOMWindow.cpp

ClusterFuzz has detected this issue as fixed in range 41295:41323.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_asan_chrome_v8_ignition
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !ThreadState::current()->isGCForbidden() in ScriptWrappableVisitor.cpp
  blink::ScriptWrappableVisitor::TracePrologue
  v8::internal::IncrementalMarking::StartMarking
  
Regressed: V8: r41193:41199
Fixed: V8: r41295:41323

Minimized Testcase (0.36 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv96gjvfT2Y1HNTOsawy3dKRq1RwiiYI5rqeS8dFtvljE1gx692WD0g6A3z8Bq7PI9r4FTRjwJ8gc9tYj4-1Rqgm1qIrtBso8pIErZolTd_FP7_xEYJ0y1zZnCw6I0jPBL83_Xi2NCPbUa1DqsbMrUFOzuhKpFg?testcase_id=5428050075582464
<script>
   function __f_12(nest) {
    var __v_14 = [];
    for (var __v_12 = 0; __v_12 < nest; ++__v_12)
        __v_14.push('* > ');
}
__f_12(400000);
Object.prototype.foo = function() {
  top.postMessage('PASS: Called the correct method.', '*');
}
  top.postMessage('ready', '*');
window.addEventListener('message', function() {
  Object.prototype.foo();
});
</script>


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.