SUMMARY Okular 1.3.3 viewing PDF files under Ubuntu 18.04 STEPS TO REPRODUCE 1. Do something with keyboard or mouse BY ACCIDENT. I have no idea what it is; I am certainly not trying to Zoom and sometimes am trying to switch to another program. This may perhaps involve the mouse wheel, but I am not sure. Do this while viewing a book of say 100 pages or more. 2. Okular interprets this as a request to zoom to 1600%. There is no way to configure the Zoom drop box to restrict the zoom range. 3. OBSERVED RESULT Suddenly, out of the blue, the Zoom box displays 1600% and the computer locks up for several minutes. You cannot interrupt the process. I have a 2-core laptop and a 4-core laptop and on both of them the whole machine seizes up: music and videos stop playing or stutter to a stop, nothing else responds, the mouse may not track. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Liux Ubuntu `8.04 (available in About System) KDE Plasma Version: ? KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION
Could not reproduce. Even going to a zoom of 10000% isn't very slow. I also cannot accidentally zoom.
I'll make this bug NEEDSINFO
Created attachment 156141 [details] attachment-1453721-0.html How can you NOT reproduce this? Are you trying it on a 1-page document? Try it on a 500-page book instead. I just tried it with a 500 page book using Okular 21.12.3 on Ubuntu 22.04 on a 1.6 GHz laptop. I stopped counting when it hit two minutes. The obvious approach is to render the current page at the new size, then when you move to a new page, render that, and so on. Instead, okular acts as if it is re-rendering the whole document in the new size. As for accidentally, the trick is to be using a laptop where a slight flexing of the case causes the machine to hallucinate mouse clicks and key presses. It can also happen if you are *trying* to zoom in but release the mouse button at the wrong time. What I *really* want is the ability to replace the menu of sizes with a list of sizes of my own choosing. On Sat, 11 Feb 2023 at 02:20, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=424224 > > fw.smit01@gmail.com changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |fw.smit01@gmail.com > > --- Comment #1 from fw.smit01@gmail.com --- > Could not reproduce. Even going to a zoom of 10000% isn't very slow. I also > cannot accidentally zoom. > > -- > You are receiving this mail because: > You reported the bug.
I tried it on a few >500 page books, but it renders almost instantly and doesn't lock up during the rendering. What is your memory usage doing during the rendering? Maybe it gets filled up, leading to swapping. I used Okular Version 22.12.0
Created attachment 156206 [details] attachment-1730213-0.html "What is my memory usage doing during the rendering?" How could I possibly tell? The machine is basically unresponsive until it's done. Possibly relevant: the machine I'm doing this on has 4 GB of memory and when I reported the issue had a 1TB hard drive. Now it has a 1TB SSD and the delay is much less. Still long enough to be frustrating, though. On Mon, 13 Feb 2023 at 23:54, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=424224 > > --- Comment #4 from fw.smit01@gmail.com --- > I tried it on a few >500 page books, but it renders almost instantly and > doesn't lock up during the rendering. What is your memory usage doing > during > the rendering? Maybe it gets filled up, leading to swapping. > > I used Okular Version 22.12.0 > > -- > You are receiving this mail because: > You reported the bug.
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!