Version: 0.12.2 (using KDE 4.6.2) OS: Linux I'm experiencing very unpleasant bug in okular which leads to X11 session hang up in response to attempt of scrolling pdf or djvu document. Reproducible: Sometimes Steps to Reproduce: I have no exact recepie to reproduce this. It happens with variety of djvu documents (which i probably shouldn't post here due to copyright laws). The only regularity i have found is that freeze happens in the moment i'm pressing page up/down to scroll the page. Actual Results: X11 hang ups or working extremely slowly. The disk usage led is blinking constantly. I've tried to login in text mode, but couldn't wait till my zsh session is loaded after I login/password is finally typed in. Ctrl-Alt-Backpase is the only thing helping me this case. The last accident impelled me to post this bug is that this time okular freezed my system completely (capslock indicator stopped to switch). This is the file i was browsing that moment http://mmcs.sfedu.ru/~ulysses/IT/Haskell/papers/why-haskell-censored.pdf it was opened in presentation mode (not like all previous documents). Also incidentally faced exactly the same bug while using another computer with KDE4. I'm not shure, but i think it was running Fedora.
Is it possible that you just have too few memory and your system is running out of RAM?
I opened the file and scrolled through it -- no lockups here. But there could be some memory issues if you're RAM is tight, though. As I was reading the file you sent, I had 'top' running: rekonq's resident memory (RES column) went from ~160M to 300M as I paged through the file. When I closed the tab it went back to ~150M right away.
Maybe this is the problem. I remember running like two or three okular instances and firefox that times (i have 2gb ram and no swap). And there was chromium with dosens of opened tabs on that desktop (which seemed to be very powerfull). Then it is strange that high memory consumption leads to such hangups. Is it something like elusive 12309 thing or just okular bug?
Can you still reproduce this bug with Okular >= 0.19.0 ( KDE >= 4.13.0 )? We have changed some things about memory management since then. Thanks for caring about Okular :)
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 set the bug status 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!
Thank you all for you kind support. I'm sure the original problem has gone away by now, so this can be closed.