https://bugs.kde.org/show_bug.cgi?id=388854
Brennan Kinney <polarathene-sig...@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Resolution|INVALID |---
CC| |polarathene-signup@hotmail.
| |com
Status|RESOLVED |REOPENED
--- Comment #19 from Brennan Kinney <polarathene-sig...@hotmail.com> ---
I can confirm a memory leak on Manjaro KDE with Okular 1.4.2. I've come here
from the reddit discussion:
https://www.reddit.com/r/kde/comments/8v4g5y/extremely_high_ram_usage_by_okular/
4 page document(90KB in size, e-mail with few small images like logos and
icons) using about 28MB RAM when opened.
Repeatedly scrolling up and down this document increases memory usage, I
stopped at 60MB, it's not freeing or re-using existing memory, that doesn't
seem like it's caching content properly.
I imagine one could continue this process until all RAM is used or something
triggers a cleanup. I'm not seeing any noticeable or major memory increase
while the document is idle/inactive, nor CPU usage. When scrolling rapidly
(drag scrollbar top to bottom) CPU usage was initially displaying 9% up to 14%
when I reached 60MB, this value was consistent at increasing steadily with the
RAM. This is probably single-threaded and would cap at 25% requiring more time
to process what should be linear time.
Additional memory should not be allocated like this, there would be a limit if
it were caching properly and utilizing that, the CPU activity is likely
associated with the memory leak.
--
You are receiving this mail because:
You are watching all bug changes.
