Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
poppler
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 613
    • Issues 613
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 39
    • Merge Requests 39
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • poppler
  • poppler
  • Issues
  • #774

Closed
Open
Opened May 31, 2019 by Alex K@alexk

pdftocairo generates PS that crashes Adobe engine

When some PDFs are converted to PS by pdftocairo using cairo 1.15.10 or later, the resulting PS files crash printers that are using Adobe PS engine. In my case, Ricoh printers.

Adobe reviewed the PS files and said this:

Cairo incorporates pattern data into form data. When printing, the form data is drawn repeatedly, but the cache memory overflows because the pattern data is included. Due to this, an illegal memory access occurs and the job is canceled.

If Cairo does not include pattern data in the form data, it is possible to work around the problem.

Does this pattern data need to be included in the form? Perhaps it's still possible to return to 1.15.8 behavior, or pinpoint the commit that I could remove just for my environment?

Here are two example PDF files, and two resulting PS files for each PDF.

Cairo 1.15.8

pdftocairo -ps -level3 pwc.pdf pwc158.ps

pdftocairo -ps -level3 sub.pdf sub158.ps

Cairo 1.16.0 (I'm using 1.16.0 in this example, but the issue occurs with 1.15.10 onward).

pdftocairo -ps -level3 pwc.pdf pwc160.ps

pdftocairo -ps -level3 sub.pdf sub160.ps

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: poppler/poppler#774