This was reported in https://bugzilla.gnome.org/show_bug.cgi?id=728998 -------------------------- When I scroll document, it takes more than a minute to show a page, during this time one of cpu cores is fully loaded. Another pdf viewer works well. Link to a file https://mega.co.nz/#!1donRahR!r01FPw3DHI7dpW09biJXydlYsbDlF3H_sPE63BqldQw -------------------------- I can reproduce the problem with poppler-glib-demo and qt4-demo using Arthur (0.26).
What about splash? (Arthur backend is not production ready really, so you shouldn't be really using it for anything)
Splash renders the document as expected (I forgot to mention it). I tested with all of them only to check in which product to file the bug. I will keep in mind for the future to not test against Arthur.
Seems to be "cairo backend" problem only: I can open it in okular without seeing that problem, and time measurement shows me: time ./utils/pdftoppm -png -cropbox -f 1 -l 10 78016.open/lecture4.pdf output/78016 real 0m6.556s user 0m6.516s sys 0m0.016s (which is a reasonable time because of the usage of pattern colorspaces, but:) time ./utils/pdftocairo -png -cropbox -f 1 -l 10 78016.open/lecture4.pdf output/78016-cairo real 2m52.166s user 2m45.826s sys 0m6.012s
With master it takes my PC 157 seconds to render the first 10 pages with pdftocairo. With the patch at bug 33364 it takes 32 seconds.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/46.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.