New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 901613 link

Starred by 1 user
Status: Assigned
Owner:
█ qingsi@google.com
Last visit > 30 days ago
Cc:
█ mflodman@webrtc.org
kwiberg@webrtc.org
henrika@webrtc.org
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in mdns_parser_fuzzer

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

Fuzzer: libFuzzer_mdns_parser_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  mdns_parser_fuzzer
  
Sanitizer: address (ASAN)

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

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

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 3

Cc: kwiberg@webrtc.org mflodman@webrtc.org henrika@webrtc.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 2 by ClusterFuzz, Nov 3

Labels: Test-Predator-Auto-Owner
Owner: qingsi@google.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://webrtc.googlesource.com/src/+/558b93b3e9a176a737ffea9de069eaa3184e5d2f (Add the multicast DNS message format.).

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

Labels: OS-Windows
Project Member

Comment 4 by ClusterFuzz, Dec 1

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

Comment 5 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 6 by ClusterFuzz, Dec 7

Labels: OS-Chrome
Project Member

Comment 7 by ClusterFuzz, Dec 21

Labels: OS-Mac
►

Sign in to add a comment