Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Could someone please take a look?.
Thank you.

I synced to 55.0.2883.105, followed the instructions for Libfuzzer + MSan and the test ran successfully in 15s. I can try something else if someone has a suggestion.

If the run-time of this test is based on wall clock, then something else running on the same core could easily push this past the time-out.

We've upgraded Hunspell to 1.6.0, which includes many upstream and our own optimizations, in 57. I suspect that we don't want to back-port, so not sure what to do about this issue.

If the runtime in 57 is significantly shorter than the 15s you reported, let's close it.

If it isn't: Looking up a suggestion shouldn't take 15 seconds under MSan. Do we have an idea what's happening before the timeout? 

The time isn't much better in 57. The problem is that this particular fuzz is a word that is (I'm estimating) 90 chars long. (I'm sure you know) suggest() has these things it tries, like swapping each pair of chars, which for 90 chars would add up. According to callgrind, a single call to suggest() results in 12 million look-ups (for this test.)

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

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