Bug 156779 - PDF (link supplied) brings Okular to it's knees
Summary: PDF (link supplied) brings Okular to it's knees
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-27 14:52 UTC by Nick Warne
Modified: 2008-01-27 19:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Warne 2008-01-27 14:52:13 UTC
Version:            (using 4.00.80 (KDE 4.0.80 >= 20080104), compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-g9b73e76f

Using the PDF supplied from link below (downloaded to local drive!!):

http://www.omegawatches.com/uploads/tx_omega/English.pdf

It loads pretty fast, but then trying to navigate, it keeps Okular busy for 10 - 20 seconds each time with 100% CPU time.  It will eventually catch up until scrolling to the next few pages.  This happens each scroll.

If you are brave enough, trying to print a page then makes Okular takes ages to do any thing @ 100% CPU time.

I do not have background fill/transparency set for printing, and use the 'Normal (default) memory performance option.

Nick
Comment 1 Pino Toscano 2008-01-27 15:16:12 UTC
Cannot reproduce the huge slowdown, it loads and renders pretty fast (but using Poppler HEAD).
Which version of Poppler are you using?
Comment 2 Nick Warne 2008-01-27 15:35:57 UTC
poppler-0.6.3

Umm, just looking, poppler 0.6.4 was released yesterday.

Let me try that.

Nick
Comment 3 Nick Warne 2008-01-27 17:20:12 UTC
OK, still the same issue.

I tried various other PDF's I have (166 pages with text graphics, various with lots of images, various with lots of graphics and diagrams etc.) and all perform excellently.

Loading the Omega PDF just grounds Okluar to a standstill - in some instances up to a minute between going to next page with CPU at 100%.

Is there anything I can do to see what it is up to during this period of 100% CPU time?

Nick
Comment 4 Nick Warne 2008-01-27 19:15:34 UTC
Using latest GIT from 27th Jan 2008 does indeed resolve this issue.

Nick