Direct-leak in v8::internal::Isolate::FindOrAllocatePerThreadDataForThisThread |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6298680535810048 Fuzzer: libfuzzer_pdfium_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: v8::internal::Isolate::FindOrAllocatePerThreadDataForThisThread v8::internal::Isolate::Enter v8::Isolate::New Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95LL9Jmo0XygAOpJfSdEEaHQwEA01iOa6a-Ub9aj2xaC5-wlvFV0awTEJY6nhqoVst3TOYIO_sIZhyqibxq3RRMxFsj28OuKlnXO4wiqXUjsHQ_UWC-sEztpRwFXO_uLB3fqI5WJ5PPVb_GUFzNmmPfa2oSYQ?testcase_id=6298680535810048 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Oct 20 2016
jochen@ could this be a v8 leak, or is it because we're not correctly freeing something on the PDFium side?
,
Oct 21 2016
,
Oct 31 2016
,
Nov 3 2016
ClusterFuzz has detected this issue as fixed in range 428862:429212. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6298680535810048 Fuzzer: libfuzzer_pdfium_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: v8::internal::Isolate::FindOrAllocatePerThreadDataForThisThread v8::internal::Isolate::Enter v8::Isolate::New Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=425682:425723 Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=428862:429212 Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95LL9Jmo0XygAOpJfSdEEaHQwEA01iOa6a-Ub9aj2xaC5-wlvFV0awTEJY6nhqoVst3TOYIO_sIZhyqibxq3RRMxFsj28OuKlnXO4wiqXUjsHQ_UWC-sEztpRwFXO_uLB3fqI5WJ5PPVb_GUFzNmmPfa2oSYQ?testcase_id=6298680535810048 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.
,
Nov 3 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 22 2016
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 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mmohammad@chromium.org
, Oct 19 2016Status: Assigned (was: Untriaged)