Summary: | Opening PDF results in 36.5% of my 8gb memory used | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Aranjedeath <orangewinds> |
Component: | PDF backend | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | aacid, luigi.toscano |
Priority: | NOR | ||
Version: | 0.20.0 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
URL: | https://mirror.explodie.org/texts/africa-global-politics-pan_african-perspective.pdf | ||
Latest Commit: | Version Fixed In: |
Description
Aranjedeath
2014-09-22 22:24:13 UTC
Do you have some specific settings in your okular configuration? Can you try with a different user? Is the "normal" package from Debian testing? I just tried here (up-to-date Debian testing as well, same 0.20.0, poppler 0.26.4) and I see this as ps auxw: prova 16435 5.5 1.5 647840 125244 pts/14 S+ 00:30 0:02 okular https://mirror.explodie.org/texts/africa-global-politics-pan_african-perspective.pdf RSS is definitely acceptable (less than 200MB) Yes, using distribution standard everything. I don't know what popplar is, I'm using 0.20.0, with kde 4.14.1. Very interesting. I just went through the settings and it says somehow I've got the performance memory usage setting on "greedy" not "normal". Not sure how that happened. When reset to "normal" it only uses 1.6% memory. dorotea 26112 35.2 35.0 3414088 2874404 ? Sl 15:39 0:47 /usr/bin/okular vs dorotea 25918 1.5 1.6 682444 131740 ? S 15:37 0:01 /usr/bin/okular also it takes a full 1 minute for the ram to max out at 36.5% used. Hmm. Maybe this is my fault, then? But still that's a lot of ram to use. I am not sure i understand you. You told okular to be greedy with memory use and now you're opening a bug because it's greedy? I don't remember setting it that way, but sure I'll allow your premise. Yes. Opening more than 1 pdf, or (for example) having chrome open on any normal computer (simultaneously) seems pretty likely to result in an OOM scenario, in which Okular would be at fault for causing. Because most debian based linux distributions (ubuntu et all, I'm getting at user-count on desktop here, not some other finer detail) compile out the OOMkiller feature from their kernels, there's nothing a regular user can do but sit while their computer is locked up. Talk about a horrendous user experience. I suppose my wishlist feature is that this become more intelligent, and not screw over users if it can be avoided. You set a memory mode that says clearly in the docu that will use up to 50% of your ram, you can't complain is using 37% of it. |