Assigning to mmoroz@ for the recent work on Issue 569578 and help in further investigation of this.

Strange, looks like some random flakiness to me. new() has been called in unique_ptr constructor in libc++, I think there cannot a leak.

Also I cannot reproduce it neither with my local build nor with the build downloaded from CF.

Kicked off redo "Fixed". CC'ing Kostya and Mike.

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=5707715502669824

Fuzzer: base_json_reader_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  thread<void
  StartRssThread
  FuzzerDriver
  

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94RKGvCwyrIyx8kK3Z5r-kX41zc2jGyMAmkAADp54BrzLAbFb2nAwsbPGwI9JciYqg7vee-qxXno-Rb1_X2tvMtQ258AToBAYC6whaF6Qk6JSV9wAtljErqIfpgAGTdSexM0oWm_iKVrpm5yPJByIOuln370A


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

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

Interesting. The leak report is coming from libFuzzer itself... 

And can you reproduce it locally? 

I cannot reproduce it neither with my local build nor with the build downloaded from CF :(

Looks like CF also thinks that this is flaky...

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=5707715502669824

Fuzzer: base_json_reader_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  thread<void
  StartRssThread
  FuzzerDriver
  

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94RKGvCwyrIyx8kK3Z5r-kX41zc2jGyMAmkAADp54BrzLAbFb2nAwsbPGwI9JciYqg7vee-qxXno-Rb1_X2tvMtQ258AToBAYC6whaF6Qk6JSV9wAtljErqIfpgAGTdSexM0oWm_iKVrpm5yPJByIOuln370A


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

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

ClusterFuzz testcase is verified as fixed, closing issue.

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

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