New issue
Advanced search Search tips

Issue 820835 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Timeout in hit_test_query_fuzzer

Project Member Reported by ClusterFuzz, Mar 11 2018

Issue description

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

Fuzzer: libFuzzer_hit_test_query_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  hit_test_query_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=541959:541976

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 11 2018

Labels: OS-Mac
Project Member

Comment 2 by ClusterFuzz, Mar 11 2018

Labels: Test-Predator-Auto-Owner
Owner: sadrul@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ad8ab8fd70189c757e710a5b7335c8bf8be7188b (viz hit test: Add a fuzzer for hit-test-query.).

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: sadrul@chromium.org
 Issue 827920  has been merged into this issue.
Project Member

Comment 4 by ClusterFuzz, Apr 4 2018

Components: Internals>Compositing Internals>Skia
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 5 by bugdroid1@chromium.org, Apr 4 2018

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

commit 9d4d1fef05cca5398d6ae8dfbd6c5f552bff6389
Author: Sadrul Habib Chowdhury <sadrul@chromium.org>
Date: Wed Apr 04 21:48:05 2018

viz: Fix the fuzzer for hit-test query.

Impose a limit on the depth of the embedding, to avoid a stack overflow
during the generation of the hit-test data phase.

BUG= 820835 

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I07f3dbb5422458db703661b421b315e1ca4784dd
Reviewed-on: https://chromium-review.googlesource.com/993033
Reviewed-by: Ria Jiang <riajiang@chromium.org>
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#548214}
[modify] https://crrev.com/9d4d1fef05cca5398d6ae8dfbd6c5f552bff6389/components/viz/host/hit_test/hit_test_query_fuzzer.cc

Project Member

Comment 6 by ClusterFuzz, Apr 6 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5742538183671808 is verified as fixed, so closing issue as verified.

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

Comment 7 by ClusterFuzz, Apr 7 2018

ClusterFuzz has detected this issue as fixed in range 548195:548215.

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

Fuzzer: libFuzzer_hit_test_query_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  hit_test_query_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=541959:541976
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=548195:548215

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

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

Comment 8 by ClusterFuzz, Apr 7 2018

ClusterFuzz has detected this issue as fixed in range 548195:548215.

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

Fuzzer: libFuzzer_hit_test_query_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  hit_test_query_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=541959:541976
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=548195:548215

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

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

Comment 9 by ClusterFuzz, Apr 7 2018

ClusterFuzz has detected this issue as fixed in range 548195:548215.

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

Fuzzer: libFuzzer_hit_test_query_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  hit_test_query_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=541959:541976
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=548195:548215

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

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.

Sign in to add a comment