https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #57 from Franz Berger <fberger.w...@gmail.com> ---
I just did some testing, using a ~800 pages long document and okular 4.13.0 and
xorg-server-1.15.1 on Gentoo amd64.
On my desktop, using proprietary Nvidia drivers, I can easily make okular use
5GiB+ of memory (according to htop's "RES" column) by scrolling for a minute.
However, the memory seems to be completely released after closing okular, and
does not seem to increase Xorg memory usage (as was the case a few years ago).
Xrestop only shows 20k of memory used by the process.
On my laptop, using open source Intel drivers, scrolling for a minute or two
results in high (easily 1GiB) pixmap memory usage in Xrestop (instead of being
directly attributed to okular in htop). Again, the memory gets freed after
closing okular and does not have any apparent effect on Xorg memory usage.
Also, it seems that okular will not eat into swap, but will limit memory usage
automatically instead (tested by opening a couple of large documents
simultaneously).
Note: The above tests were performed using "normal" memory usage setting
("aggressive" gives similar results).
Personally, I am happy to see that the allocated memory no longer seems to
persist after closing okular (which was my main issue), though I'm not sure how
much memory okular should reasonably be allowed to occupy on "normal" memory
usage settings.
Hope this helps.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel
