New issue
Advanced search Search tips

Issue 907662 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Breakpoint in base::PickleIterator::ReadLong

Project Member Reported by ClusterFuzz, Nov 21

Issue description

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

Fuzzer: libFuzzer_pickle_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: Breakpoint
Crash Address: 0x000000000000
Crash State:
  base::PickleIterator::ReadLong
  pickle_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=610080:610107

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 21

Components: Internals>Core
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, Nov 21

Labels: Test-Predator-Auto-Owner
Owner: amistry@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/7404c058244b48008231f057b9e779e07f49eebc (Add fuzzer for base::PickleIterator.).

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.
Jonathan, this is another Windows specific crash :)
Project Member

Comment 4 by ClusterFuzz, Nov 26

Labels: Fuzz-Blocker ReleaseBlock-Beta M-72
This crash occurs very frequently on windows platform and is likely preventing the fuzzer pickle_fuzzer 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.
Sigh! sizeof(long) == 4 on windows (https://msdn.microsoft.com/en-us/library/s3f49ktz.aspx), so the checked_cast<long>(int64_t) will CHECK-fail on anything outside the int32 range. This appears to be intentional behaviour.
Labels: -ReleaseBlock-Beta ClusterFuzz-Wrong
-RBB, not a release issue.
Labels: -M-72
Project Member

Comment 8 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5462484657635328 appears to be flaky, updating reproducibility label.
Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
The documentation for reproducing on Windows has been moved to https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md

Sign in to add a comment