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

Issue 897935 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Ill in v8::internal::BaseConsumedPreParsedScopeData<v8::internal::PodArray<unsigned cha

Project Member Reported by ClusterFuzz, Oct 22

Issue description

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Ill
Crash Address: 0x557da220b65e
Crash State:
  v8::internal::BaseConsumedPreParsedScopeData<v8::internal::PodArray<unsigned cha
  v8::internal::Parser::SkipFunction
  v8::internal::Parser::ParseFunctionLiteral
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=56847:56848

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 22

Components: Blink>JavaScript>Parser
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Oct 22

Labels: Test-Predator-Auto-Owner
Owner: sattlerf@google.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/4e18f8685ba87fce771791b97896ee55e90e0d70 ([scanner] Add error state to scanner to prevent further processing.).

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

Comment 3 by bugdroid1@chromium.org, Oct 23

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

commit e91e18041a3716e3ea1de9ed927618a3c5e68160
Author: Florian Sattler <sattlerf@google.com>
Date: Tue Oct 23 14:39:19 2018

[scanner] Fix apply for bookmarks and usage of scope_data within an error context.

Bug: chromium:897815,  chromium:897935 , chromium:897766
Change-Id: Ie8c4105867f84054559a4c43c23be82365502c1e
Reviewed-on: https://chromium-review.googlesource.com/c/1296469
Reviewed-by: Marja Hölttä <marja@chromium.org>
Reviewed-by: Toon Verwaest <verwaest@chromium.org>
Commit-Queue: Florian Sattler <sattlerf@google.com>
Cr-Commit-Position: refs/heads/master@{#56905}
[modify] https://crrev.com/e91e18041a3716e3ea1de9ed927618a3c5e68160/src/parsing/parser.cc
[modify] https://crrev.com/e91e18041a3716e3ea1de9ed927618a3c5e68160/src/parsing/scanner.cc
[modify] https://crrev.com/e91e18041a3716e3ea1de9ed927618a3c5e68160/src/parsing/scanner.h
[add] https://crrev.com/e91e18041a3716e3ea1de9ed927618a3c5e68160/test/mjsunit/regress/regress-897815.js

Project Member

Comment 4 by ClusterFuzz, Oct 24

ClusterFuzz has detected this issue as fixed in range 56904:56905.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Ill
Crash Address: 0x557da220b65e
Crash State:
  v8::internal::BaseConsumedPreParsedScopeData<v8::internal::PodArray<unsigned cha
  v8::internal::Parser::SkipFunction
  v8::internal::Parser::ParseFunctionLiteral
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=56847:56848
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=56904:56905

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

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 5 by ClusterFuzz, Oct 24

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