ICEpdf
  1. ICEpdf
  2. PDF-866

High CPU load when trying to render pages in PDF

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.2
    • Fix Version/s: 6.0
    • Component/s: Core/Parsing
    • Labels:
      None
    • Environment:
      All

      Description

      With the provided PDF, there is a high CPU load when trying to render the contents of the PDF file. No errors are thrown and after leaving the viewer for 10-15 min, the page content still doesn't show.

        Activity

        Hide
        Patrick Corless added a comment -

        The file in question uses type 3 fonts. And there appears to be a parsing issue while interpreting one of the inline images which puts the parser into an infinite loop,

        Show
        Patrick Corless added a comment - The file in question uses type 3 fonts. And there appears to be a parsing issue while interpreting one of the inline images which puts the parser into an infinite loop,
        Hide
        Patrick Corless added a comment -

        The image in question is indeed inline but it's actually not the data stream that 's the problem but some rather strange postscript in the dictionary of the inline image: "[null<</K -1/Columns 16>>]"

        Show
        Patrick Corless added a comment - The image in question is indeed inline but it's actually not the data stream that 's the problem but some rather strange postscript in the dictionary of the inline image: " [null<</K -1/Columns 16>>] "
        Hide
        Patrick Corless added a comment -

        The parsing error is related to the fact the image array tokens were not white space separated as expected. I've make a small tweak to the content parser which addresses this issue. Still need a full QA run but don't expect any problems.

        Because of the use of Type 3 fonts, the font rendering quality can be improved by using the system property -Dorg.icepdf.core.imageReference=smoothScaled

        Show
        Patrick Corless added a comment - The parsing error is related to the fact the image array tokens were not white space separated as expected. I've make a small tweak to the content parser which addresses this issue. Still need a full QA run but don't expect any problems. Because of the use of Type 3 fonts, the font rendering quality can be improved by using the system property -Dorg.icepdf.core.imageReference=smoothScaled

          People

          • Assignee:
            Patrick Corless
            Reporter:
            Arran Mccullough
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: