New issue
Advanced search Search tips

Issue 901203 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 9
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: written_bytes2 > 0u in paint_op_buffer_eq_fuzzer.cc

Project Member Reported by ClusterFuzz, Nov 2

Issue description

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  written_bytes2 > 0u in paint_op_buffer_eq_fuzzer.cc
  __scrt_common_main_seh
  paint_op_buffer_eq_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=602543:602564

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 2

Labels: Fuzz-Blocker ReleaseBlock-Beta M-72
This crash occurs very frequently on windows platform and is likely preventing the fuzzer paint_op_buffer_eq_fuzzer.exe from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.
Project Member

Comment 2 by ClusterFuzz, Nov 2

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 3 by ClusterFuzz, Nov 2

Labels: Test-Predator-Auto-Owner
Owner: enne@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e27aea347db6587ec245c68ba4c171ec54ab6e9d (cc: don't scale paint record shaders in fuzzer).

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 ClusterFuzz, Nov 9

ClusterFuzz has detected this issue as fixed in range 606550:606553.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  written_bytes2 > 0u in paint_op_buffer_eq_fuzzer.cc
  __scrt_common_main_seh
  paint_op_buffer_eq_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=602543:602564
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=606550:606553

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing_on_windows.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, Nov 9

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5878512458924032 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
The documentation for reproducing bugs on Windows was moved to: https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md

Sign in to add a comment