New issue
Advanced search Search tips

Issue 906670 link

Starred by 1 user
Status: Untriaged
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Out-of-memory in mdns_parser_fuzzer

Project Member Reported by ClusterFuzz, Nov 19 
Detailed report: https://clusterfuzz.com/testcase?key=6490692489314304

Fuzzer: libFuzzer_mdns_parser_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  mdns_parser_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=588371:588372

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

Issue filed automatically.

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

Comment 1 by kkaluri@chromium.org, Nov 20

Labels: M-71 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

Thanks!
Project Member

Comment 2 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6490692489314304 appears to be flaky, updating reproducibility label.

Comment 3 by infe...@chromium.org, Dec 1

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.
Project Member

Comment 4 by ClusterFuzz, Dec 2

Labels: OS-Mac
►

Sign in to add a comment