New issue
Advanced search Search tips

Issue 835628 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference WRITE in viz::HitTestAggregator::ResizeHitTestRegionArray

Project Member Reported by ClusterFuzz, Apr 22 2018

Issue description

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

Fuzzer: libFuzzer_hit_test_manager_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x00000000001c
Crash State:
  viz::HitTestAggregator::ResizeHitTestRegionArray
  viz::HitTestAggregator::AllocateHitTestRegionArray
  hit_test_manager_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=546214:546245

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Apr 22 2018

Components: Internals>Compositing
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, Apr 22 2018

Labels: Test-Predator-Auto-Owner
Owner: riajiang@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/337a57b9b3be8a2f7dab252c4d4d90ff44bbc2b3 (Add a fuzzer for HitTestManager and HitTestAggregator.).

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, Apr 25 2018

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

commit 26b55f3af850438b9edfa7003b3f08eb764a6d4e
Author: Ria Jiang <riajiang@chromium.org>
Date: Wed Apr 25 23:21:59 2018

Crash the gpu process when it cannot allocate shared memory.

Bug:  835628 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I06c983e2e12b804a3fd31ef909917c30d6cf1b06
Reviewed-on: https://chromium-review.googlesource.com/1027801
Commit-Queue: Ria Jiang <riajiang@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553813}
[modify] https://crrev.com/26b55f3af850438b9edfa7003b3f08eb764a6d4e/components/viz/service/hit_test/hit_test_aggregator.cc

Project Member

Comment 4 by ClusterFuzz, May 7 2018

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Status: Fixed (was: WontFix)

Sign in to add a comment