Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/52b3b491a55f5f3233ca78e0c22c37384b92670e ([errors] Use FATAL macro where possible).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

As discussed offline, this is probably a WontFix, string eval with invalid runtime function call.

ClusterFuzz testcase 4971694549368832 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 56055:56056.

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

Fuzzer: ochang_js_fuzzer_win
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Fatal error
Crash Address: 
Crash State:
  NULL
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=51276:51277
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=56055:56056

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

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

0690342238

Le lundi 9 juillet 2018, ClusterFuzz via monorail <
monorail+v2.2757933724@chromium.org> a écrit :