CHECK failure: vertex_attrib_manager_count_ == 0u in vertex_array_manager.cc |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5913159882506240 Fuzzer: libFuzzer_gpu_raster_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: vertex_attrib_manager_count_ == 0u in vertex_array_manager.cc gpu::gles2::VertexArrayManager::~VertexArrayManager gpu::raster::RasterDecoderImpl::~RasterDecoderImpl Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=564082:564104 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5913159882506240 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jun 4 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Jun 4 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/a57031bb7aa798eae315a81face9b6b95300ca84 (Plumb oop_rasterization_supported). 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.
,
Jun 4 2018
,
Jun 4 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/15dbca378583113b91a9faa8edff92eeaa5aca7e commit 15dbca378583113b91a9faa8edff92eeaa5aca7e Author: Jonathan Backer <backer@chromium.org> Date: Mon Jun 04 20:39:33 2018 Clean up RasterDecoderImpl on early exit Copying the same pattern from GLES2DecoderImpl. If Initialize fails, call Destroy directly instead of relying on the caller to clean up. Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Change-Id: Id2827f3bfb4831bb49ca24b8b70a86a574eaea88 Reviewed-on: https://chromium-review.googlesource.com/1085893 Reviewed-by: Zhenyao Mo <zmo@chromium.org> Commit-Queue: Jonathan Backer <backer@chromium.org> Cr-Commit-Position: refs/heads/master@{#564220} [modify] https://crrev.com/15dbca378583113b91a9faa8edff92eeaa5aca7e/gpu/command_buffer/service/raster_decoder.cc
,
Jun 4 2018
,
Jun 5 2018
ClusterFuzz has detected this issue as fixed in range 564197:564224. Detailed report: https://clusterfuzz.com/testcase?key=5913159882506240 Fuzzer: libFuzzer_gpu_raster_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: vertex_attrib_manager_count_ == 0u in vertex_array_manager.cc gpu::gles2::VertexArrayManager::~VertexArrayManager gpu::raster::RasterDecoderImpl::~RasterDecoderImpl Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=564082:564104 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=564197:564224 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5913159882506240 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.
,
Jun 5 2018
ClusterFuzz testcase 5913159882506240 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 |
||||||
Comment 1 by ClusterFuzz
, Jun 4 2018Labels: ClusterFuzz-Auto-CC