New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 672172 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Hang in pdfium_fuzzer

Project Member Reported by ClusterFuzz, Dec 7 2016

Issue description

Components: Internals>Plugins>PDF
Labels: Test-Predator-Wrong M-57
Cc: msrchandra@chromium.org
Owner: tsepez@chromium.org
Status: Assigned (was: Untriaged)
Unable to find the possible suspect using CL from find it.
From the regression range assigning to the concern owner.
https://chromium.googlesource.com/chromium/src/+log/dbbd35e36767126cd0632d4a4abb521f7efc8eb2..f1b58e59add1ada98d78b6b883da1952e0712fd5?pretty=fuller


@tsepez -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Cc: tsepez@chromium.org
Owner: npm@chromium.org
I'm guessing (based on pure speculation other than we've had trouble with this CL before):

https://codereview.chromium.org/2470803003/

npm if you're around, you might want to try to confirm otherwise I can do so on monday.

Comment 4 by npm@chromium.org, Jan 3 2017

Status: Started (was: Assigned)
Yes, me. Looks like there's a cycle on the pages dictionary or something, and the page traversal is looping.
Project Member

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

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

commit 1b132220ee62f68ddec8463f83e9bd357dbc503d
Author: pdfium-deps-roller <pdfium-deps-roller@chromium.org>
Date: Tue Jan 03 20:47:00 2017

Roll src/third_party/pdfium/ 05f541279..db194cf01 (2 commits).

https://pdfium.googlesource.com/pdfium.git/+log/05f541279ec0..db194cf01806

$ git log 05f541279..db194cf01 --date=short --no-merges --format='%ad %ae %s'
2017-01-02 dsinclair Use return values in CFWL_Scrollbar instead of out params
2017-01-03 npm Force stop of page tree traversal when max level reached

BUG= 672172 

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/2608233003
Cr-Commit-Position: refs/heads/master@{#441203}

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

Comment 6 by npm@chromium.org, Jan 3 2017

Status: Fixed (was: Started)
Project Member

Comment 7 by ClusterFuzz, Jan 4 2017

ClusterFuzz has detected this issue as fixed in range 441152:441210.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5586013947953152

Fuzzer: libfuzzer_pdfium_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout
Crash Address: 
Crash State:
  pdfium_fuzzer
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=430008:430067
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=441152:441210

Minimized Testcase (1.40 Kb): https://cluster-fuzz.appspot.com/download/AMIfv955g0EYzWyqTf9ZWYzK8TmOAn4ELZ7u3Qs0AMWOhHUtDkWTi9EYc2WWHsQky2kPpJSKBVa1QY23bsXKpdcUyub8hl6BRy0Kwa3teTuSgbVdWJ4FoFQ7fX7vNoDZxZeuZ8-46yKtxny342Ah1z8zHD3zPAdhrA?testcase_id=5586013947953152

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.

Sign in to add a comment