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

Issue 826690 link

Starred by 1 user
Status: Verified
Owner:
infe...@chromium.org
Closed: Apr 2018
Cc:
█ brajkumar@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Timeout in string_tokenizer_fuzzer

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

Fuzzer: libFuzzer_string_tokenizer_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  string_tokenizer_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=545925:545931

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

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 29 2018

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

From the below CL observing some changes related to 'string_tokenizer_fuzzer.cc' , hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/c1022fce2628003b41923b7eef64341427c4c7ee..2b66e9c46f7739a46093c4468e9bdc98b16ddc69?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/3277b80e5f0fa6ccdcf4c8e85be8b54b2dc66f36

inferno@ -- 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, Apr 14 2018

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

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

Sign in to add a comment