Bug 76821 - Render is very slow for some files
Summary: Render is very slow for some files
Status: RESOLVED DUPLICATE of bug 90171
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-31 08:28 UTC by Anatoly
Modified: 2016-03-17 14:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Visualization of a part of a call graph (169.17 KB, text/plain)
2014-03-31 08:28 UTC, Anatoly
Details
Visualization of a part of a call graph (169.17 KB, image/png)
2014-03-31 08:30 UTC, Anatoly
Details

Description Anatoly 2014-03-31 08:28:54 UTC
Created attachment 96640 [details]
Visualization of a part of a call graph

Problem is similar to https://bugs.freedesktop.org/show_bug.cgi?id=66928.

Tested on poppler-0.25.2
Configuration: ./configure --prefix=/usr --sysconfdir=/etc \
      --localstatedir=/var --disable-static \
      --enable-cairo-output \
      --enable-xpdf-headers \
      --enable-libjpeg --enable-zlib \
      --enable-poppler-qt4 \
      --enable-poppler-glib

Example file located here https://razor.blackbeam.org/x.pdf (sorry for expired certificate).
Also here is callgrind output https://razor.blackbeam.org/callgrind.out (can be viewed with kcachegrind).

Also i attached a call graph visualization.

cmsDoTransform is called 6814 times which i think is reasonable due to height of an image on pdf page. But some funcs from liblcms2 and libm is called more then 100 000 000 times.
Comment 1 Anatoly 2014-03-31 08:30:38 UTC
Created attachment 96641 [details]
Visualization of a part of a call graph
Comment 2 Anatoly 2014-03-31 08:32:57 UTC
Render is 61 seconds for both pdftoppm and pdftocairo.
Comment 3 Thomas Freitag 2016-03-17 14:30:55 UTC

*** This bug has been marked as a duplicate of bug 90171 ***


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.