Related to  bug 522018 .

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

Fuzzer: tokenfuzz_pdf_april16
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race on vptr READ 8
Crash Address: 0x7d0400002f10
Crash State:
  base::FileTracing::ScopedEnabler::ScopedEnabler
  base::File::File
  sessions::SessionBackend::OpenAndWriteHeader
  

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96yrETNYbzOkDUX2-ovlfiAUGEXCe9r7mA0_z1AQNH0go4Xi4bI9xzuwL6MTYoC-EEM_-ClwxkGqFLuy5iC_B8Ec3vDfRyGgeWkPH9uW3PHKhw3MGblT2newF71_nNN15suxmYDkKUOvuoJJlwiLu1bcaOOZxIE9zxhxG0NiphnEqyGan4


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