Ocular safer from memory leaks. Due to my job, I need to keep Ocular open for a lot of hours, even days. At the time of writing this report, on my openSUSE desktop, Ocular has reserved 750MB of RAM for a document of 1.4MB! Ocular runs for 36 hours. 24 hours ago, at the same time of the day, Ocular had reserved 500MB of RAM. Reproducible: Always Steps to Reproduce: 1. Open a document in Ocular 2. Navigate though the document, as you normally do. 3. Stop reading the document and record memory consumption. 4. Wait for a few hours and record memory again. You will notice a significant increase. Expected Results: Memory consumption should stay stable through time.
Created attachment 93927 [details] Screenshot of memory usage
So you only ever open one file?
Only on file open. Due to my job, I need to keep Okular for a lot of time, some times days. The settings are the defaults. Also, it's indepedent from the file. I tried with 5 different files. Some of them freely available, others, just documents that I had "printed" from LibreOffice. I will check with my Fedora 22 (KDE 5) if there is a similar situation.
(In reply to Peter Tselios from comment #3) > Only on file open. Due to my job, I need to keep Okular for a lot of time, > some times days. > The settings are the defaults. Also, it's indepedent from the file. I tried > with 5 different files. Some of them freely available, others, just > documents that I had "printed" from LibreOffice. > > I will check with my Fedora 22 (KDE 5) if there is a similar situation. I can verify that it's the same and in KDE 5 with Okular 0.22
There's no such thing as KDE 5, i guess you mean the desktop is Plasma 5, but that makes no difference for Okular itself. Can you attach any of those files you use to reproduce the problem? Also what is your pattern of usage? Just leave the file open? Scroll between pages? I.e. what do you exactly do to reproduce the problem?
I will try to post some files. I cannot post those files that I use daily because they contain sensitive data. The pattern is simple: - Open document. - Start reading document (usually at Fit Width zoom level) - Scroll down Copy text - More scroll down - At some point stop and move to another open application - Return after minutes or hours.
Also you may want to try running okular throught valgrind --tool=massif okular And attach the file so we can see the memory evolution pattern
OK, I will try that in a few days. Do you prefer to do that in KDE 4 or 5?
It doesn't matter if you run Okular in Plasma 4 or Plasma 5. If possible make sure you have debug symbols installed since that will help in giving more info,
Peter, any success in running Okular with valgrind memory profiling tools? You might also look at the new heaptrack tool.
No answer for years