This issue happens in 88% of fuzzer runs: https://clusterfuzz.com/v2/performance-report/libFuzzer_hunspell_fuzzer/libfuzzer_chrome_asan/latest

It's a blocker for gaining new code coverage and performing an efficient continuous testing.

How is it possible that spellchecker needs more than 25 seconds to process 112 bytes of input?

Kevin and Rachel, could you please take a look or suggest another owner?

Hi Max,

Yes, the spellchecker really needs 25 seconds to do that test. The new version of hunspell has an n-squared algorithm for (iirc) finding a close match. We had talked about having it not bother even looking if the length was beyond a certain amount, but that would depend on language, etc. and we've handed over hunspell to another group. Perhaps Rachel could suggest a person.

Just to update, providing Predator results --
Regression information is not available. The result is the blame information. 

Author: tfarina
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/ea6469cb1f800b1795493822dbe932a03a51d554
Time: Fri May 01 00:31:43 2015
The CL last changed line 380 of file bdict_reader.cc, which is stack frame 3. 

Author: tfarina
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/ea6469cb1f800b1795493822dbe932a03a51d554
Time: Fri May 01 00:31:43 2015
The CL last changed line 753 of file bdict_reader.cc, which is stack frame 4. 

Author: tfarina
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/ea6469cb1f800b1795493822dbe932a03a51d554
Time: Fri May 01 00:31:43 2015
The CL last changed line 207 of file hashmgr.cxx, which is stack frame 5. 

Author: krb
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/047b36f906a4d3b957a2d7869eb41cdd74027fcb
Time: Tue Dec 13 15:41:23 2016
The CL last changed line 3659 of file affixmgr.cxx, which is stack frame 6. 

Author: krb
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/047b36f906a4d3b957a2d7869eb41cdd74027fcb
Time: Tue Dec 13 15:41:23 2016
The CL last changed line 1730 of file affixmgr.cxx, which is stack frame 7. 

Author: krb
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/047b36f906a4d3b957a2d7869eb41cdd74027fcb
Time: Tue Dec 13 15:41:23 2016
The CL last changed line 1627 of file suggestmgr.cxx, which is stack frame 8. 

Author: krb
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/047b36f906a4d3b957a2d7869eb41cdd74027fcb
Time: Tue Dec 13 15:41:23 2016
The CL last changed line 275 of file suggestmgr.cxx, which is stack frame 9.

Could some one please look into the issue and update.
Thank You.

ClusterFuzz testcase 4677425790451712 is flaky and no longer reproduces, so closing issue.

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

Re-opening the issue as it seems to happen in 75% of runs: https://clusterfuzz.com/v2/performance-report/libFuzzer_hunspell_fuzzer/libfuzzer_chrome_asan/latest

We might consider limiting max length of the input.

 Issue 767334  has been merged into this issue.

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

(bulk edit)

We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future.

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

ClusterFuzz testcase 5727464886894592 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.