Try e.g. this document: http://tinyurl.com/p3su6cp . (It's Intel's System Programming Guide). It opens in about 25 seconds on my machine with Okular. For comparison, Adobe Reader 9.5.1 opens this same document nearly instantly — less than in one second! Reproducible: Always Steps to Reproduce: 1. Download the example document linked above 2. Try opening it with Okular 3. Wait until it shows the first page 4. (optional) Try the same in Adobe Reader and see how amazingly fast it shows the document Actual Results: First page showed after ~25 seconds waiting for seemingly hung Okular Expected Results: The document should open nearly instantly, as is the case with Adobe Reader. This was checked on Kubuntu 12.04 with its stock KDE and Kubuntu 14.04 with its stock KDE version. User experience is the same.
Kubuntu 14.10 utopic $ okular --version Qt: 4.8.6 KDE: 4.14.2 Okular: 0.20.2 libpoppler-qt4-4: Installiert: 0.26.5-0ubuntu2 ~ 3 or 4 seconds to display the downloaded pdf (9 MB)
Which poppler version are you using?
0.24.5-2ubuntu4 on Kubuntu 14.04 0.18.4-1ubuntu3.1 on Kubuntu 12.04 0.33.0 on LFS All they show qualitatively the same problem.
Do you have a remote printer that is unplugged?
All remote printers I have are plugged in. But the problem also reproduces with network down.
Is okular using 100% of your CPU? Or just sitting there doing nothing?
Uses 100% of a single core (i.e. 25% total on a quad-core machine).
Just tried running sysprof with it, it appears to take most of the time in DecryptStream::lookChar(). On the machine I'm now, with Kubuntu 14.04, it takes 4-5 seconds to open the file, within which sysprof did the sampling.
I'm confused now, you're saying that it takes 5 seconds or 25?
On one machine (LFS with poppler 0.33.0) it takes 25 seconds, on this one (Kubuntu 14.04 with poppler 0.24.5) it's 5.
Did you do the sysprof sampling in that machine that is fast? Why?
Yes, I did it on the fast one, because it's near me. I'll get to the other one after several hours. Should I try profiling there too?
Yes, i'm not interested in profiling on a computer where there's nothing to fix.
So you consider 5 seconds vs almost instant as in Adobe Reader a negligible difference?
Do you consider 25 seconds vs 5 seconds a negligible difference?
Created attachment 93820 [details] Sysprof log OK, now I got to this machine with 25 seconds opening. Here the log is more verbose due to better-installed debug symbols or whatever (and it doesn't contradict my observations on the faster machine). I attach the syslog saved log.
The big slowliness has been fixed by the newer poppler release as we can see. I can't see any huge difference between the time Adobe takes to open the file and the time Okular takes to open the file in my system. We can leave this open in case you feel the difference is bad but i wouldn't hold my breath on getting someone to look at it. Maybe you can? You seem to know a bit about technical stuff.
If I'm not mistaken, 0.33 should be newer than 0.24. Am I wrong?
@Albert What time does it take for Okular to open the file on your system? And what OS, poppler and Okular versions are you using? I can't seem to figure out in which version of what it should work without slowdowns. All systems I tried appeared too slow to me (5 seconds is also slow, since even MuPDF opens it instantly, even on the machine with Okular's 25 seconds.)
(In reply to Ruslan Kabatsayev from comment #18) > If I'm not mistaken, 0.33 should be newer than 0.24. Am I wrong? No, you're correct. (In reply to Ruslan Kabatsayev from comment #19) > @Albert > What time does it take for Okular to open the file on your system? And what > OS, poppler and Okular versions are you using? I can't seem to figure out in > which version of what it should work without slowdowns. All systems I tried > appeared too slow to me (5 seconds is also slow, since even MuPDF opens it > instantly, even on the machine with Okular's 25 seconds.) 4 seconds. poppler 0.35 Okular 0.22.90 mupdf opens it instantly because it basically does "nothing" poppler/qt4/tests/test-poppler-qt4 also opens it in 86 milisseconds, but showing the big table of contents, etc is costly. I'd say there's something wrong in your LFS build.
Does it still take you a long time to open the document with a more recent version of Okular?
(In reply to Blase Johnson from comment #21) > Does it still take you a long time to open the document with a more recent > version of Okular? Still 4 seconds with the document from comment 0 on Kubuntu 18.04. And I don't have any TOC panel open.
I can open that document in about 2 seconds.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
The information requested in comment #21 was added with comment #22; changing status for inspection.
There is a way to use MuPDF as backend in Okular, [1] and it can render the pages in the test document (Intel's System Programming Guide) very quickly. [1] https://github.com/gustawho/okular-backend-mupdf
Created attachment 147993 [details] video of slow PDF page rendering Okular 21.12.3 Qt Versione 5.15.3 (compilato con 5.15.3) KDE Frameworks Versione 5.92.0 I get this slow PDF page rendering issue on recently-scanned Archive.org PDFs. Not all scanned PDFs have this issue for me; it seems to be just the ones with layers. (DjVus are much faster!)