New issue
Advanced search Search tips

Issue 816289 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug

Blocking:
issue 815622



Sign in to add a comment

Fatal error in Runtime_TypedArrayCopyElements

Project Member Reported by ClusterFuzz, Feb 25 2018

Issue description

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

Fuzzer: ochang_js_fuzzer_win
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Fatal error
Crash Address: 
Crash State:
  
  v8::platform::PrintStackTrace
  v8::internal::Runtime_TypedArrayCopyElements
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=51376:51377

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 25 2018

Labels: Test-Predator-Auto-Owner
Owner: petermarshall@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/81a3742a889db5db034b8345683cef49e95095ee ([typedarray] Port TypedArray.from to CSA.).

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.
Cc: jgruber@chromium.org
Status: Started (was: Assigned)
Summary: Fatal error in Runtime_TypedArrayCopyElements (was: Fatal error in )
Project Member

Comment 4 by bugdroid1@chromium.org, Feb 26 2018

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

commit 6b25ab2e8cc557c5efd64312330726f6614370d4
Author: Peter Marshall <petermarshall@chromium.org>
Date: Mon Feb 26 15:51:31 2018

[typedarray] Extend ElementsAccessor::CopyElements to all Object types

Previously, Strings without an iterator would go to the runtime path
and fail on because it expected a JSReceiver type. This was in-line
with what the elements accessor expected. We can actually handle all
object types in the final slow path (using LookupIterator) so it is no
problem to change the accept types.

Bug:  chromium:816289 
Change-Id: Iebb8de0bb7551aee3894c8a23836d079c93726a7
Reviewed-on: https://chromium-review.googlesource.com/937461
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Commit-Queue: Peter Marshall <petermarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#51574}
[modify] https://crrev.com/6b25ab2e8cc557c5efd64312330726f6614370d4/src/elements.cc
[modify] https://crrev.com/6b25ab2e8cc557c5efd64312330726f6614370d4/src/elements.h
[modify] https://crrev.com/6b25ab2e8cc557c5efd64312330726f6614370d4/src/runtime/runtime-typedarray.cc
[add] https://crrev.com/6b25ab2e8cc557c5efd64312330726f6614370d4/test/mjsunit/regress/regress-816289.js

Blocking: 815622
Project Member

Comment 6 by ClusterFuzz, Feb 27 2018

ClusterFuzz has detected this issue as fixed in range 51573:51574.

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

Fuzzer: ochang_js_fuzzer_win
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Fatal error
Crash Address: 
Crash State:
  
  v8::platform::PrintStackTrace
  v8::internal::Runtime_TypedArrayCopyElements
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=51376:51377
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=51573:51574

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

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

Comment 7 by ClusterFuzz, Feb 27 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Started)
ClusterFuzz testcase 6325006355922944 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