https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #22 from Rooty <zy...@gmx.us> --- (In reply to Brennan Kinney from comment #21) > (In reply to Nate Graham from comment #20) > > Thanks for the additional information, Brennan. However, as previously > > noted, high memory usage of the sort described by you and others in this > > ticket is not considered a bug because: > > 1. it's only done when there's actually unused memory available > > 2. Okular should give it up when the system is under memory pressure > > 3. you can change the memory caching aggressiveness in the settings if this > > sort of thing unnerves you > > > > If you're seeing that any of the above conditions are not working properly, > > please file a new bug report to track that issue. Thanks! > > Nate, it's not just caching, there is an obvious leak/growth, a 90kb PDF of > 4 pages, 30MB on open, steadily rising memory usage by scrolling repeatedly > through the pages up/down. This growth only stops once the scrolling does, > and will resume again by scrolling. The cache is not being used, memory is > just being allocated for the content again, and again, instead of reused or > freed(until the mentioned memory pressure). > > I could continue that process for the same file and bring the memory usage > up for the single document from the 60MB I got it to 1GB or 10GB without > issue from the looks of it. That's not good behaviour, even if it is freed > at a later point, the application shouldn't balloon memory like that > pointlessly. If others think that is appropriate, it's a bit of a worry. > Don't claim it as working as intended when it's clearly poor memory > handling. It's ok to admit that this behaviour is happening and that it is > not correct, but not see any value or importance in investing time to > correct it, just don't pretend that it's allocating hundreds to thousands of > MB in memory for small documents from scrolling pages when that growth is > constant and does not stop, Okular is not using that memory in it's > entirerity, it's not an optimization, it's a bug. i use mostly chromium to read very large medical textbooks and medical research that has tons of imaging in it, it's absolute torture to have okular take up most of my RAM to open up a 200 MB PDF... this wouldn't be a problem if other software behaved the same way (so yeah, it might not be a bug, but it certainly is a design flaw) if the memory caching settings in okular are changed, the pages become far less responsive, and it makes it that much harder to navigate through the document -- You are receiving this mail because: You are the assignee for the bug.
