New issue
Advanced search Search tips

Issue 843074 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug

Blocking:
issue 62400



Sign in to add a comment

Timeout in pdf_fm2js_fuzzer

Project Member Reported by ClusterFuzz, May 15 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6309397157117952

Fuzzer: libFuzzer_pdf_fm2js_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  pdf_fm2js_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=558429:558434

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6309397157117952

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, May 15 2018

Components: Internals>Plugins>PDF
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, May 15 2018

Cc: dsinclair@chromium.org jam@chromium.org brucedaw...@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 3 by ClusterFuzz, May 15 2018

Labels: Test-Predator-Auto-Owner
Owner: dsinclair@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://pdfium.googlesource.com/pdfium/+/77c223be193b303b833053a757a2f1f2534da610 (Use internal wcstof instead of system wcstod in formcalc lexer).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Blocking: 62400
Status: Started (was: Assigned)
Project Member

Comment 6 by bugdroid1@chromium.org, May 15 2018

The following revision refers to this bug:
  https://pdfium.googlesource.com/pdfium/+/6137483528225c1dc102db44fb2c2bce6c256534

commit 6137483528225c1dc102db44fb2c2bce6c256534
Author: Dan Sinclair <dsinclair@chromium.org>
Date: Tue May 15 18:59:46 2018

Cap size of exponent when converting floats

When detecting the exponent on a floating point number, cap the maximum
amount we'll multiply by otherwise we can get excessivly large numbers.

Bug:  chromium:843074 
Change-Id: I6a8d1b4c20b66e305d2727f464119b1e74beb699
Reviewed-on: https://pdfium-review.googlesource.com/32570
Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Commit-Queue: dsinclair <dsinclair@chromium.org>

[modify] https://crrev.com/6137483528225c1dc102db44fb2c2bce6c256534/core/fxcrt/fx_extension.cpp
[modify] https://crrev.com/6137483528225c1dc102db44fb2c2bce6c256534/core/fxcrt/fx_extension_unittest.cpp

Status: Fixed (was: Started)
Project Member

Comment 8 by bugdroid1@chromium.org, May 16 2018

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

commit ab05dd5e5e0e6c793780030ff09a0477fcf05f94
Author: pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Wed May 16 02:42:38 2018

Roll src/third_party/pdfium/ 473b4ae48..c3aa483e1 (8 commits)

https://pdfium.googlesource.com/pdfium.git/+log/473b4ae489e8..c3aa483e1325

$ git log 473b4ae48..c3aa483e1 --date=short --no-merges --format='%ad %ae %s'
2018-05-15 dsinclair Remove unused methods from CFX_BreakLine
2018-05-15 dsinclair Remove CFX_BreakLine::CountPieces
2018-05-15 dsinclair Remove CFX_BreakLine::CountChars
2018-05-15 tsepez Use {{streamlen}} macro in testing/resources/javascript/*.in
2018-05-15 dsinclair Cap size of exponent when converting floats
2018-05-15 tsepez Use {{trailer}} macro in testing/resources/javascript/*.in
2018-05-15 tsepez Test app.beep() in standalone PDFium.
2018-05-15 dsinclair Break CPDF_CotnentParser::Continue into pieces

Created with:
  roll-dep src/third_party/pdfium
BUG= chromium:843074 


The AutoRoll server is located here: https://pdfium-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=dsinclair@chromium.org

Change-Id: I09f12f06499f54f5d38ab9de9c464ee56229cfce
Reviewed-on: https://chromium-review.googlesource.com/1060462
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#558935}
[modify] https://crrev.com/ab05dd5e5e0e6c793780030ff09a0477fcf05f94/DEPS

Project Member

Comment 9 by ClusterFuzz, May 16 2018

ClusterFuzz has detected this issue as fixed in range 558933:558950.

Detailed report: https://clusterfuzz.com/testcase?key=6309397157117952

Fuzzer: libFuzzer_pdf_fm2js_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  pdf_fm2js_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=558429:558434
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=558933:558950

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6309397157117952

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 10 by ClusterFuzz, May 16 2018

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

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

Comment 11 by ClusterFuzz, May 16 2018

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

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

Sign in to add a comment