ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6230856033370112

Fuzzer: attekett_surku_fuzzer
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  std::tr1::_Hashtable<std::string, std::pair<std::string const, int>, std::alloca
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=209699:209703

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv975zoEij_I-Q_m8f6BF_f23RWbBB5LcLK5_8o55GN9s7alAOCZjhmXauKiaK676KjrFGz6mIdk_cayeakc7BTx6spo92ktu3LrPibcEq2-KUen7VYeC4P_ABG3PlQkFI7RVEHj-lesqtnwElQNYIWElOat6KK3lRTsg_3FUf-kboCts5Qk?testcase_id=6230856033370112


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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

As per comment#2, closing this issue.
Thank you.