New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 680425 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

V8 correctness failure in configs: x64,fullcode:x64,ignition_staging

Project Member Reported by ClusterFuzz, Jan 12 2017

Issue description

Cc: titzer@chromium.org
Components: -Blink>JavaScript Blink>JavaScript>WebAssembly
Labels: v8-foozzie-failure
Owner: bradnelson@chromium.org
Status: Assigned (was: Untriaged)
Also regressed with this revert:
https://chromium.googlesource.com/v8/v8/+log/f5f22cfc581a6bc52275053c0ce4d5e7cc2ad9f1..d11da92f43f1f96981cb823ea2d2c9aa23a64176?pretty=fuller

Maybe just gets fixed on reland.
Project Member

Comment 2 by ClusterFuzz, Jan 13 2017

ClusterFuzz has detected this issue as fixed in range 42287:42288.

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

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_staging
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,fullcode:x64,ignition_staging
  sources: 6fbe47d2
  
Sanitizer: address (ASAN)

Regressed: V8: r42252:42253
Fixed: V8: r42287:42288

Minimized Testcase (0.57 Kb): https://cluster-fuzz.appspot.com/download/AMIfv972bwRuL2GztXsYcVKkJPnqnAdGL2aOqjDaLXoeGtkUTw8LvsC5_2x5bM27_nqdUOKT-DmtQ6Sc3PqETj2hbswcg5Biea_pUBFnVimLs3B5aaESeiPbYhwaPbCx_NjIabyTOZZuxq5X2oG5qWSDD36-UdBTGKrJljaysAhldkfHvSZNEtyTGmt01DP-p-LOActaJJiF1ym7XosDW4eErV0mo_FUy1m_lRfrW3X7oMB-J-NS2UPUdx9csGMtdBcRf4a6EjQ3tUVI0yINcihHXtEQow-8RPNVQTpUB1Ltw05G_4UXFG5u1aaUKpCV4xSGeDjrnIePYdlNb7c-GvaC38tn6xVt54I-eJW-6w6I40k8dAhShALYpmQ1D0tnFLs5lKBNveya2RERnK8yyUZGR9C6ihYv9A?testcase_id=6352599495475200

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.
Project Member

Comment 3 by ClusterFuzz, Jan 13 2017

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

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

Sign in to add a comment