New issue
Advanced search Search tips

Issue 797233 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

CHECK failure: ptr_ in scoped_refptr.h

Project Member Reported by ClusterFuzz, Dec 22 2017

Issue description

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  ptr_ in scoped_refptr.h
  scoped_refptr<gpu::gles2::TexturePassthrough>::operator->
  gpu::gles2::GLES2DecoderPassthroughImpl::DoDeleteTextures
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=522788:522809

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 22 2017

Components: Internals>Core Internals>GPU>Internals
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, Dec 22 2017

Labels: Test-Predator-Auto-Owner
Owner: geoffl...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/42c78a82903338fb92e11dd4121a7db81139f578 (Use ClientServiceMap for TexturePassthrough objects.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 3 by bugdroid1@chromium.org, Jan 5 2018

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

commit d4e22f508556f04f027b196d786c8a4d2d3b4024
Author: Geoff Lang <geofflang@chromium.org>
Date: Fri Jan 05 21:50:01 2018

Check for null texture objects when deleting textures.

The zero texture is a valid client ID but has no associated texture
object.

BUG= 797233 
BUG= 797251 

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ia8dce1d8b03b16560f06d9b3203ffc0c53459919
Reviewed-on: https://chromium-review.googlesource.com/852432
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#527395}
[modify] https://crrev.com/d4e22f508556f04f027b196d786c8a4d2d3b4024/gpu/command_buffer/service/gles2_cmd_decoder_passthrough_doers.cc

Project Member

Comment 4 by ClusterFuzz, Jan 6 2018

ClusterFuzz has detected this issue as fixed in range 527385:527421.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  ptr_ in scoped_refptr.h
  scoped_refptr<gpu::gles2::TexturePassthrough>::operator->
  gpu::gles2::GLES2DecoderPassthroughImpl::DoDeleteTextures
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=522788:522809
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=527385:527421

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

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 5 by ClusterFuzz, Jan 6 2018

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