[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 --- Comment #16 from Martin Bednar --- Patched okular on my Gentoo. Seems fixed. Thank you! You made the day of at least 2 people :) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Tobias Deiminger changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||okular/commit/593803b0a1d98 ||eba64aac38316aa521130b4ae78 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #15 from Tobias Deiminger --- Git commit 593803b0a1d98eba64aac38316aa521130b4ae78 by Tobias Deiminger. Committed on 30/01/2020 at 08:15. Pushed by aacid into branch 'release/19.12'. Fix render stop and high load due to timing issue Text generation is connected to pixmap generation thread started signal. However the signal may have been emitted faster than the connect could took place, and because started is fired only once, the connected lambda never got executed. generatePixmap tried to sync up with that never happening text generation anyway by means of scheduling itself. This lead to a infinite loop via a no more sleeping QEventLoop. Fixed by moving the connect in front of starting the thread. Related: bug 396137, bug 403643 M +2-2core/generator.cpp https://invent.kde.org/kde/okular/commit/593803b0a1d98eba64aac38316aa521130b4ae78 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Martin Bednar changed: What|Removed |Added CC||martin+...@serafean.cz --- Comment #14 from Martin Bednar --- Created attachment 125514 --> https://bugs.kde.org/attachment.cgi?id=125514=edit PDF endless CPU usage I think I'm in the same boat with the attached PDF. Okular CPU usage never drops under 100% (on one core, I think it would take even more if it could) After a few tries it rendered completely though (CPU usage not dropping)... Poppler version 0.82.0 Okular 1.9.1 (kde-applications-19.12.1) KDE Frameworks 5.66.0 Qt 5.13.2 (built against 5.13.2) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #13 from Xwang --- I have the same problem with some PDF with Arch linux. Okular version 1.9.0 KDE Frameworks 5.64.0 Qt 5.13.2 (compiled with 5.13.2) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Logan Rathbone changed: What|Removed |Added CC||popro...@gmail.com --- Comment #12 from Logan Rathbone --- I am not sure if this is the same, but I feel that I have experienced something similar for some time. Sometimes, a documents just suddenly stops loading at a certain page number. I then close Okular, but the process continues to run, at 100% cpu usage. The only resolution appears to be to kill the process. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 --- Comment #11 from Albert Astals Cid --- I'm 93% sure this is a duplicate of 396137 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Jan Przybylak changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Jan Przybylak changed: What|Removed |Added CC||jplx...@gmail.com --- Comment #10 from Jan Przybylak --- I can confirm this issue as well. When zooming in on a 4.7MiB, 2-page PDF containing a large bitmap image (it's a scan), everything becomes pixelated and stops loading. Okular's memory usage went up to over a gigabyte, with about 25% CPU usage as well. It also spawned a second process which was stuck at ~25% and didn't stop when I closed the window. Running Okular from the terminal reveals that it somehow runs out of memory: org.kde.okular.core: Running out of memory on page 1 (17333x25160 px); This does not happen in other PDF readers like Xreader and Evince, which allow me to zoom in and move around all I want. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 --- Comment #9 from Filip Fila --- Still happens with Okular 1.8.2, Plasma 5.16.5, KF 5.62, Qt 5.13.1. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Marko changed: What|Removed |Added CC||cami...@gmail.com --- Comment #8 from Marko --- Happens here too. Opening Okular either directly by clicking a pdf in Dolphin or via web browser does the same. After seemingly closing it it continues to run in the background consuming your cpu. I wouldn't even have noticed if hadn't a lot of transcodes running and they were going much slower than they should have been. After manually killing the Okular processes the resources they were consuming are released and everything works fine. Arch Linux KDE Plasma version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.9-1-ck-haswell OS Type: 64-bit i5 4460 cpu 32GB ram -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru --- Comment #7 from Alexander Kandaurov --- I investigated this a bit and it looks like what causes the hang is the QTimer::singleShot() call from Generator::generatePixmap() which keeps an endless cycle of firing and resetting the same timer. I also experienced a hang once on closing a document (the window has closed but the process remained eating 25% of CPU) where it got stuck in DocumentPrivate::clearAndWaitForRequests() on loop.exec() call where it also kept firing that generatePixmap() timer. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 --- Comment #6 from Filip F. --- I had a lock up today reading a 15 page article and when I checked the system monitor Okular was again stuck at 25% CPU usage, with the ram spiking up to 2GB at that point (it's 160 MB with this document when there are no problems). It unfroze itself not long after though, maybe because it's not as demanding of a document. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 --- Comment #4 from Filip --- Poppler version is: 0.64.0-1 And here is the video: https://youtu.be/DCwekaSAnIk It took me a while to get it to show up on recording... there is no sure-shot way of reproducing this. You can see that I was very aggressive with scrolling and zooming, but it can happen in a more of a real life situation. The 25% CPU lock-up and the process not dying are also shown in the video. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||aa...@kde.org --- Comment #3 from Albert Astals Cid --- Which poppler version does Manjaro use? Can you record a video so i can see the kind of scrolling you do? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Rooty changed: What|Removed |Added CC||zy...@gmx.us --- Comment #2 from Rooty --- yeah the same thing happens to me in okular 1.4.2 with its memory usage set to "Low" (despite this, its memory usage slowly clambers up to a gig or so), except the CPU usage goes up to 40% or so, and it's intermittent hence hard to reproduce if i use it for long enough, after a while it stops rendering pages -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 --- Comment #1 from Filip --- BTW the performance profile used was Normal. -- You are receiving this mail because: You are the assignee for the bug.
