Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P poppler
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 656
    • Issues 656
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 43
    • Merge requests 43
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • poppler
  • poppler
  • Issues
  • #352

Closed
Open
Created Jul 15, 2013 by Bugzilla Migration User@bugzilla-migration

poppler doesn't cache heavy objects

Submitted by Pavel Ignatov

Assigned to poppler-bugs

Link to original bug (#66938)

Description

When displaying huge pages they are usually rendered piece by piece using calls to the page_renderer::render_page() with appropriately calculated resolution and coordinates. When for example a pdf-page contains a huge jpeg 2000 imgage it can take several dozens of seconds to render. It seems it because on every render poppler restores a bitmap for this jpeg 2000 from scratch. As a result, when the viewer which renders big pages piece by piece spends dozens of seconds on every page scroll.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking