Crash in base::debug::DebugBreak |
|||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6043452971417600 Fuzzer: libfuzzer_gpu_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: UNKNOWN Crash Address: 0x03e90000510c Crash State: base::debug::DebugBreak gpu::gles2::QueryManager::Query::MarkAsActive gpu::gles2::TimeStampQuery::QueryCounter Sanitizer: address (ASAN) Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=428837:429212 Minimized Testcase (0.19 Kb): https://cluster-fuzz.appspot.com/download/AMIfv957LA5qg2Acbz1Xf08Z9TXVwvE4jkcn1yK26cqwey2bP1ooRz5ivHmWgJVmTCKXIk4OphAYxtvU1KpQcXUBtmQrYn5wk7SV5EspAimcamUYn7VI1QMvjiLC_neaMQ51rbn-7JpMSW5hKANEjfVYP44D5vC_yg?testcase_id=6043452971417600 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Jan 6 2017
The test case appears to be corrupt. It downloads as "fuzz-2-gpu_fuzzer" and is a binary file. Could you please look into this?
,
Jan 23 2017
Assigning an owner to hopefully answer question on comment#2.
,
Jan 24 2017
+ Abhishek for further inputs on c#2. Thank you!
,
Mar 8 2017
ClusterFuzz has detected this issue as fixed in range 455091:455226. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6043452971417600 Fuzzer: libfuzzer_gpu_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: UNKNOWN Crash Address: 0x03e900001336 Crash State: base::debug::DebugBreak gpu::gles2::QueryManager::Query::MarkAsActive gpu::gles2::TimeStampQuery::QueryCounter Sanitizer: address (ASAN) Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=428837:429212 Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=455091:455226 Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95kfnKwyYeJ8-_pk4n0VJndcy_C43_wUmAWEWNnm2eKALfDF2ogZWIPc_MLHKiFIgo_LDIl-CnOfTYxKTOCuhGgnbL5tFVtFHe5GOyzMN18QkFsrkukmCw_xTwgFcdgbbL2xMnI8LI6p7fLjcTDgMbU-HVOvGHFr5uCPrVnMbXPQ9vhiior_vqxb55Xo57garApiyLnHC3rYY6gXGGabnMyG0SrNiWE28A06kBOyiaw7QGR0DDT2dBCwtGd3Ds1nENA0UvLEqHFhOCAKd8ktEXwgv9o1KEUlxu4VgDYQ-0bFT2A-oj32W6FvV0FnqPrdyFcKoIa49jiplzE75sh9aajDrdOZMr_-v-76SSHLDZFFTC6Xnw?testcase_id=6043452971417600 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Mar 8 2017
Thank you for providing more feedback. Adding requester "kbr@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 8 2017
ClusterFuzz testcase 6043452971417600 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Apr 21 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mummare...@chromium.org
, Jan 6 2017Components: Internals>GPU
Labels: Test-Predator-Wrong M-56