New issue
Advanced search Search tips

Issue 804006 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Ill in v8::Utils::ReportApiFailure

Project Member Reported by ClusterFuzz, Jan 19 2018

Issue description

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

Fuzzer: libFuzzer_renderer_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Ill
Crash Address: 0x000009b5d97e
Crash State:
  v8::Utils::ReportApiFailure
  v8::Utils::ApiCheck
  blink::V8ContextSnapshot::EnsureInterfaceTemplatesForWorld
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=530538:530562

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Jan 19 2018

Components: Blink>Bindings Blink>JavaScript
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, Jan 19 2018

Labels: Test-Predator-Auto-Owner
Owner: peria@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/9aff02e57fa82b584e238390f1739ff410dfd377 (gin: Make v8_context_snapshot.bin as a default snapshot blob).

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 ClusterFuzz, Jan 21 2018

Labels: OS-Mac
Project Member

Comment 4 by bugdroid1@chromium.org, Jan 22 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8b6254d72354e61e9976d1b0817477689ec9eec7

commit 8b6254d72354e61e9976d1b0817477689ec9eec7
Author: Hitoshi Yoshida <peria@chromium.org>
Date: Mon Jan 22 00:50:13 2018

bindings: Enable V8ContextSnasphot on fuzzers

Currently fuzzer does not load v8_context_snapsot.bin, and
fail to set up blink.
This CL makes fuzzers to load v8_context_snapshot.bin
to work with it.



Bug:  789964 , 804073 , 804006 
Change-Id: I332586ccaf9d348fc5af3e22acdaf579624575e5
Reviewed-on: https://chromium-review.googlesource.com/876744
Reviewed-by: Oliver Chang <ochang@chromium.org>
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#530795}
[modify] https://crrev.com/8b6254d72354e61e9976d1b0817477689ec9eec7/content/test/fuzzer/BUILD.gn
[modify] https://crrev.com/8b6254d72354e61e9976d1b0817477689ec9eec7/content/test/fuzzer/fuzzer_support.cc

Project Member

Comment 5 by ClusterFuzz, Jan 22 2018

ClusterFuzz has detected this issue as fixed in range 530794:530795.

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

Fuzzer: libFuzzer_renderer_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Ill
Crash Address: 0x000009b5d97e
Crash State:
  v8::Utils::ReportApiFailure
  v8::Utils::ApiCheck
  blink::V8ContextSnapshot::EnsureInterfaceTemplatesForWorld
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=530538:530562
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=530794:530795

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Comment 6 by peria@chromium.org, Jan 22 2018

Status: Fixed (was: Assigned)
Project Member

Comment 7 by ClusterFuzz, Jan 22 2018

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