New issue
Advanced search Search tips

Issue 847526 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

CHECK failure: bound_ in test_context_provider.cc

Project Member Reported by ClusterFuzz, May 29 2018

Issue description

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  bound_ in test_context_provider.cc
  viz::TestContextProvider::GrContext
  paint_op_buffer_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=562316:562318

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 29 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, May 29 2018

Cc: enne@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 3 by ClusterFuzz, May 29 2018

Labels: Test-Predator-Auto-Owner
Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/315f2fd68d9b44ad050a581993e36dbd2f49ee33 (cc/gpu: Plumb bits required for font analysis from gpu.).

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 4 by bugdroid1@chromium.org, Jun 1 2018

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

commit 372be78fdc56b2228370a171f6b80f9af3ccf37a
Author: Khushal <khushalsagar@chromium.org>
Date: Fri Jun 01 01:27:45 2018

cc: Bind ContextProvider in PaintOpBufferFuzzer.

R=enne@chromium.org

Bug:  847526 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I77a33e72c93b17432946aa40a87533b957bd8a25
Reviewed-on: https://chromium-review.googlesource.com/1081851
Reviewed-by: enne <enne@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#563474}
[modify] https://crrev.com/372be78fdc56b2228370a171f6b80f9af3ccf37a/cc/paint/paint_op_buffer_fuzzer.cc

Project Member

Comment 5 by ClusterFuzz, Jun 1 2018

ClusterFuzz has detected this issue as fixed in range 563471:563483.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  bound_ in test_context_provider.cc
  viz::TestContextProvider::GrContext
  paint_op_buffer_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=562316:562318
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=563471:563483

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

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 6 by ClusterFuzz, Jun 1 2018

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