New issue
Advanced search Search tips

Issue 681301 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in PixarLogSetupDecode

Project Member Reported by ClusterFuzz, Jan 14 2017

Issue description

Components: Internals>Plugins>PDF
Labels: Test-Predator-Wrong M-57
Owner: npm@chromium.org
Status: Assigned (was: Untriaged)
npm@, could you please have a look and duplicate with  issue 670928 . i don't have access the  issue 670928 . thank you.

Comment 2 by npm@chromium.org, Jan 18 2017

The issue you point to has been fixed, while this one hasn't, so it is not a duplicate.
Project Member

Comment 3 by bugdroid1@chromium.org, Jan 19 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1eccd2632893e632be32bc50c92b1c78df7150b2

commit 1eccd2632893e632be32bc50c92b1c78df7150b2
Author: pdfium-deps-roller <pdfium-deps-roller@chromium.org>
Date: Thu Jan 19 22:58:17 2017

Roll src/third_party/pdfium/ 341b5c2c1..bc8dcc3ed (2 commits).

https://pdfium.googlesource.com/pdfium.git/+log/341b5c2c1cbd..bc8dcc3ede28

$ git log 341b5c2c1..bc8dcc3ed --date=short --no-merges --format='%ad %ae %s'
2017-01-19 dsinclair Add ObservedPtrs to PWL_CREATEPARAM
2017-01-18 npm Fix leak in PixarLogSetupDecode

BUG= 681351 , 681301 

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

TBR=dsinclair@chromium.org

Review-Url: https://codereview.chromium.org/2645953003
Cr-Commit-Position: refs/heads/master@{#444875}

[modify] https://crrev.com/1eccd2632893e632be32bc50c92b1c78df7150b2/DEPS

Project Member

Comment 5 by ClusterFuzz, Jan 20 2017

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

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

Sign in to add a comment