ASSERT: m_RefCount == 0 |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6320019046400000 Fuzzer: ifratric_pdf_generic Job Type: linux_debug_chrome Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: m_RefCount == 0 Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=618786:618787 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6320019046400000 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 28
ClusterFuzz has detected this issue as fixed in range 619153:619154. Detailed report: https://clusterfuzz.com/testcase?key=6320019046400000 Fuzzer: ifratric_pdf_generic Job Type: linux_debug_chrome Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: m_RefCount == 0 Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=618786:618787 Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=619153:619154 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6320019046400000 See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 28
ClusterFuzz testcase 6320019046400000 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jan 8
Not sure why this bug appeared and disappeared. |
|||
►
Sign in to add a comment |
|||
Comment 1 by pnangunoori@chromium.org
, Dec 27Labels: M-73 Test-Predator-Wrong
Owner: thestig@chromium.org
Status: Assigned (was: Untriaged)