CHECK failure: written_bytes2 > 0u in paint_op_buffer_eq_fuzzer.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6374086857719808 Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: written_bytes2 > 0u in paint_op_buffer_eq_fuzzer.cc paint_op_buffer_eq_fuzzer.cc Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=602005:602007 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6374086857719808 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 24
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/13de7e3dc62741227c5c27a709251d1a13029491 (cc: Don't create a scaled shader for fixed scales). 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.
,
Oct 24
,
Oct 25
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e27aea347db6587ec245c68ba4c171ec54ab6e9d commit e27aea347db6587ec245c68ba4c171ec54ab6e9d Author: Adrienne Walker <enne@chromium.org> Date: Thu Oct 25 01:07:29 2018 cc: don't scale paint record shaders in fuzzer Currently we scale all such shaders and rewrite them out as fixed scale (with a local matrix). This changes the serialization process and also adds a matrix where there was not one before. For the sake of the equality fuzzer, add an option where we don't modify what we are serializing in this case. Bug: 898356 Change-Id: I433b921a6e799c2f2d912e6fa61d61bd6a82e2a8 Reviewed-on: https://chromium-review.googlesource.com/c/1298423 Reviewed-by: Khushal <khushalsagar@chromium.org> Commit-Queue: enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#602553} [modify] https://crrev.com/e27aea347db6587ec245c68ba4c171ec54ab6e9d/cc/paint/paint_op_buffer.h [modify] https://crrev.com/e27aea347db6587ec245c68ba4c171ec54ab6e9d/cc/paint/paint_op_buffer_eq_fuzzer.cc [modify] https://crrev.com/e27aea347db6587ec245c68ba4c171ec54ab6e9d/cc/paint/paint_op_writer.cc
,
Oct 30
ClusterFuzz has detected this issue as fixed in range 602552:602553. Detailed report: https://clusterfuzz.com/testcase?key=6374086857719808 Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: written_bytes2 > 0u in paint_op_buffer_eq_fuzzer.cc paint_op_buffer_eq_fuzzer.cc Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=602005:602007 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=602552:602553 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6374086857719808 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.
,
Oct 30
ClusterFuzz testcase 6374086857719808 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
, Oct 24Labels: Test-Predator-Auto-Components