New issue
Advanced search Search tips

Issue 710942 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in _cmsMallocZero

Project Member Reported by ClusterFuzz, Apr 12 2017

Issue description

Cc: dsinclair@chromium.org kcwu@chromium.org npm@chromium.org
Components: Internals>Plugins>PDF
Labels: M-59 Test-Predator-Wrong
Predator and regression range didn't given any suspected CL. could someone please take a look?
Thank you
Project Member

Comment 2 by ClusterFuzz, Apr 13 2017

Project Member

Comment 3 by ClusterFuzz, Apr 13 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 5539933726179328 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Cc: -dsinclair@chromium.org
Labels: ClusterFuzz-Wrong
Owner: dsinclair@chromium.org
Status: Assigned (was: Verified)
I don't think anything changed that would fix this, re-opening so we can verify.
Status: WontFix (was: Assigned)
Bulk-WontFixing these bugs. This was a bug on ClusterFuzz side, see bug 717534. We will start seeing new testcases auto-filed in a day or two. We can't leave these open as ClusterFuzz won't autoverify them after ClusterFuzz-Wrong label.
Labels: -ClusterFuzz-Wrong
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.

Sign in to add a comment