ICEpdf
  1. ICEpdf
  2. PDF-266

Type3 Font error and resource managment

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 4.1.4
          • Fix Version/s: 4.2
          • Component/s: Font Engine
          • Labels:
            None
          • Environment:
            Pro

            Description

            Nothing like a some type 3 font issues. The forum uses noted that the attache PDF was using to much memory so I thought I should take a quite look. The Document in question uses type3 fonts throughout, each glyph is represented by a CCITTFaxDecode image which are roughly 591x523 pixels.

            When the viewing all 149 pages of the documents using a heap size of 128MB I definitely saw some slow down and some heaving Garbage collection. There was also few page with missing content.

              Activity

              Hide
              Permalink
              Patrick Corless added a comment -

              The forum user must have be looking at the Task Manager to get the claimed memory number. When I ran ICEpdf though a profiler it used the amount of memory defined by its default system proeprties for heap usage. The extra memory seen the Task manager or likely do to resources that Java needs to load the tens of thousands of fax images.

              I did update the NFontType3 class to be a little more aggressive about freeing up the glyph content stream memory once the images had been decoded and cached. There was also an issue with deriving some glyph widths which result in a few page not being correctly parsed which is now fixed.

              Closing.

              Show
              Patrick Corless added a comment - The forum user must have be looking at the Task Manager to get the claimed memory number. When I ran ICEpdf though a profiler it used the amount of memory defined by its default system proeprties for heap usage. The extra memory seen the Task manager or likely do to resources that Java needs to load the tens of thousands of fax images. I did update the NFontType3 class to be a little more aggressive about freeing up the glyph content stream memory once the images had been decoded and cached. There was also an issue with deriving some glyph widths which result in a few page not being correctly parsed which is now fixed. Closing.

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: