New issue
Advanced search Search tips

Issue 728867 link

Starred by 1 user

Issue metadata

Status: WontFix
Merged: issue 664068
Owner:
Closed: Jun 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

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

Project Member Reported by ClusterFuzz, Jun 1 2017

Issue description

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:ia32,ignition
  sources: fda
  
Sanitizer: address (ASAN)

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
// Range error. Repro:
new Uint8ClampedArray().set({}, 1073741824);

// Only in ia32:
./repro.js:1: RangeError: Source is too large
new Uint8ClampedArray().set({}, 1073741824);
                        ^

// The minimized test case from clusterfuzz swallows the exception so that the range error suppression doesn't match.
Mergedinto: 664068
Status: Duplicate (was: Untriaged)
Labels: -Pri-1 Pri-2
Owner: machenb...@chromium.org
Status: Assigned (was: Duplicate)
Actually, I could override Uint8ClampedArray().set in the respective typed array mocks for this.
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 2 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/9b5042575c944114ed90adf781c25814c87081ca

commit 9b5042575c944114ed90adf781c25814c87081ca
Author: Michael Achenbach <machenbach@chromium.org>
Date: Fri Jun 02 13:57:55 2017

[foozzie] Mock out typed array set function to suppress range error

NOTRY=true

Bug:  chromium:728867 
Change-Id: Ie116021aab9d72d01e1532036cb5de8f4b2bd2ab
Reviewed-on: https://chromium-review.googlesource.com/522663
Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#45689}
[modify] https://crrev.com/9b5042575c944114ed90adf781c25814c87081ca/tools/foozzie/v8_mock_archs.js

Project Member

Comment 5 by ClusterFuzz, Jun 2 2017

ClusterFuzz has detected this issue as fixed in range 45688:45689.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:ia32,ignition
  sources: fda
  
Sanitizer: address (ASAN)

Fixed: V8: 45688:45689

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


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.
Status: WontFix (was: Assigned)

Sign in to add a comment