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

Issue 754122 link

Starred by 2 users
Status: WontFix
Owner:
█ fran...@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
█ msrchandra@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in v8_fuzzer::FuzzerSupport::GetIsolate

Project Member Reported by ClusterFuzz, Aug 10 2017 
Detailed report: https://clusterfuzz.com/testcase?key=4993694817320960

Fuzzer: libFuzzer_v8_regexp_parser_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  v8_fuzzer::FuzzerSupport::GetIsolate
  start
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=493100:493156

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

Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Aug 10 2017

Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong-CLs M-62
Owner: fran...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "fuzzer-support.cc" assigning to the concern owner using GIT Blame.

Suspecting Commit#
https://chromium.googlesource.com/v8/v8.git/+/f9d2c5123e0a1f550873b5f693ff13b707ff4e7b

@franzih -- Could you please look into the issue, kindly re-assign if it is not related to your changes.
Thank You.

Comment 2 by msrchandra@chromium.org, Aug 10 2017 

 Issue 754109  has been merged into this issue.
Project Member

Comment 3 by ClusterFuzz, Oct 1 2017

Components: Blink>JavaScript
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Comment 4 by mmoroz@chromium.org, Oct 24 2017 

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

(bulk edit)

Comment 5 by mbarbe...@chromium.org, Nov 7 2017

Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Project Member

Comment 6 by ClusterFuzz, Dec 5 2017

Status: WontFix (was: Assigned)
ClusterFuzz testcase 4993694817320960 is flaky and no longer crashes, so closing issue.

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

Comment 7 by ClusterFuzz, Dec 12 2017

Labels: Needs-Feedback
ClusterFuzz testcase 4535985789730816 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
►

Sign in to add a comment