Summary: | okular hangs X or whole system | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Dmitry <veprbl> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | major | CC: | fabiodurso |
Priority: | NOR | Keywords: | triaged |
Version: | 0.12.2 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Dmitry
2011-04-27 21:02:39 UTC
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. |