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

Issue 825469 link

Starred by 3 users
Status: WontFix
Owner:
metzman@chromium.org
Closed: Aug 16
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Timeout in mojo_parse_message_proto_fuzzer

Project Member Reported by ClusterFuzz, Mar 24 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5178957985742848

Fuzzer: libFuzzer_mojo_parse_message_proto_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=545489:545505

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Mar 27 2018

Cc: brajkumar@chromium.org
Components: Internals>Mojo
Labels: -Pri-1 -Type-Bug M-67 Test-Predator-Wrong Pri-2 Type-Bug-Regression
Owner: metzman@chromium.org
Status: Assigned (was: Untriaged)
Predator could not provide any possible suspects.

From the below CL observing some changes related to 'mojo_parse_message_fuzzer' , hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/ffc48921fecbba1abfa29158bb53f23f7765086c..217663e0bae441071be836c179a4c648aef2572c?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/27c6e434cef36ab378012756d372c8741cbd46ce

metzman@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!
Project Member

Comment 2 by ClusterFuzz, Aug 16

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5178957985742848 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
►

Sign in to add a comment