ICEpdf
  1. ICEpdf
  2. PDF-635

StackOverflowError thrown when rendering pdf

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 5.0.1, 5.0.2, 5.0.3
          • Fix Version/s: 5.0.4
          • Component/s: Core/Parsing
          • Labels:
            None
          • Environment:
            All
          • Salesforce Case Reference:

            Description

            The following error stacktrace is thrown when rendering a customers PDF file:

            WARNING: Error parsing content stream.
            java.lang.StackOverflowError
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
            at org.icepdf.core.util.content.a.b(Unknown Source)
                    ...

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Patrick Corless added a comment -

              The are a large number of PDF comments on the first page and the content parser is having a hard time getting around them. I'll need to take a closer look but don't think this will be problem to fix.

              Show
              Patrick Corless added a comment - The are a large number of PDF comments on the first page and the content parser is having a hard time getting around them. I'll need to take a closer look but don't think this will be problem to fix.
              Hide
              Permalink
              Patrick Corless added a comment -

              The stack over flow is due to the recursive nature of how we handle the comments and the shear number of comments on the first page. I've refactored how we parse comments so that its done in a linear fashion like other token types.

              Show
              Patrick Corless added a comment - The stack over flow is due to the recursive nature of how we handle the comments and the shear number of comments on the first page. I've refactored how we parse comments so that its done in a linear fashion like other token types.
              Hide
              Permalink
              Patrick Corless added a comment -

              Lexer fix seems to be sound, closign.

              Show
              Patrick Corless added a comment - Lexer fix seems to be sound, closign.

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: