New issue
Advanced search Search tips

Issue 765888 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

V8 correctness failure in configs: x64,ignition:x64,ignition_turbo

Project Member Reported by ClusterFuzz, Sep 16 2017

Issue description

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,ignition_turbo
  sources: 24d
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48039:48040

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: mstarzinger@chromium.org
Owner: mvstan...@chromium.org
Status: Assigned (was: Untriaged)
PTAL. Got introduced by:
https://chromium.googlesource.com/v8/v8/+/37aa13fe3b434f5fe778ab4bc69c56c6bd526383 according to bisect.
Labels: -Pri-1 Pri-2
Lower prio since it seems to be an error message problem only. Do we need to suppress it?
Project Member

Comment 3 by ClusterFuzz, Sep 20 2017

ClusterFuzz has detected this issue as fixed in range 48082:48083.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,ignition_turbo
  sources: 24d
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48039:48040
Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48082:48083

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

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.
The CL was reverted but I'll try again, will address this issue too.
Project Member

Comment 5 by ClusterFuzz, Sep 20 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5623969167441920 is verified as fixed, so closing issue as verified.

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

Sign in to add a comment