Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: sigbjornf
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/05c2d71f2c3cab4c40c3d775b304d0bbfbd166bd
Time: Fri Nov 11 06:34:16 2016
Lines 204 of file V8AbstractEventListener.cpp which potentially caused crash are changed in this cl (frame #0, "chrome_child!blink::V8AbstractEventListener::belongsToTheCurrentWorld+0x3e"). 

Lines 416 of file EventTarget.cpp which potentially caused crash are changed in this cl (frame #3, "chrome_child!blink::EventTarget::setAttributeEventListener+0xe").
Minimum distance from crash line to modified line: 0. (file: V8AbstractEventListener.cpp, crashed on: 204, modified: 204).

@sigbjornf -- 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 465765:465806.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x00000003
Crash State:
  blink::V8AbstractEventListener::belongsToTheCurrentWorld
  blink::EventTarget::getAttributeEventListener
  blink::EventTarget::clearAttributeEventListener
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=431480:431542
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=465765:465806

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv96c9N7mko142z5xnMNGgjOQA9uCoTgiDw58LpfVAltOzGB0iz3FGPqosqdTEA8KiJsF-YlbfO6Nb4Rg3ABMCCFHYFLUDkHOn-mPW6B8FiA_She5SFyl7Gs7bmOddKj7N7eWQNnxqNO5QRx55ZgUCJSKCywIWph5hrpEmGEZ9TPCaUdeo1JdxXfmZQzjcKVVy7V-n3FIq0GSF1nZlS5yIpQlqfjyh0TfNPKuepEy05jlNYqQy1IVfj_sPAAANwSD69tS4iC6b7h5E3_qEwro5n1_4324LoK0mBa2gMBrkg5qvZeb3mXKohAJMQD4wuOQ05z-D9hRsvAN9UYvBlYjgI6Ef1ZzAMmTDd-OHoow_Y3ImBE-D1H1NpQvDZc95fcaJDIha838ziM2eFRyC0UaK7MR7xDPwA?testcase_id=5960418473541632


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

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