https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #10 from barray ---
Created attachment 140612
--> https://bugs.kde.org/attachment.cgi?id=140612&action=edit
Valgrind log after running for quite a few hours on built source
It was horrifically slow, but I tried to use it as normal
https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #9 from barray ---
Created attachment 140591
--> https://bugs.kde.org/attachment.cgi?id=140591&action=edit
Replicated RAM usage issue in a debug build
As you can see, I am now able to replicate the RAM usage issue in a debug
bui
https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #8 from barray ---
(In reply to Laurent Montel from comment #7)
> You rebuild akregator but it seems that it uses
> akregator_config_userfeedback.so from your system not you install directory.
> If you rebuild remove your akreg
https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #6 from barray ---
Created attachment 140567
--> https://bugs.kde.org/attachment.cgi?id=140567&action=edit
RAM usage over time for built-from-source version
This is the built-from-source version - the issue doesn't appear
https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #5 from barray ---
I have built from source (v20.12.3) and am now making sure it still replicates.
If so, I plan to get a better valgrind output - as well as confirm the issue in
later versions.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #3 from barray ---
Created attachment 140528
--> https://bugs.kde.org/attachment.cgi?id=140528&action=edit
Valgrind log after running akgregator for a few hours
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #2 from barray ---
Created attachment 140527
--> https://bugs.kde.org/attachment.cgi?id=140527&action=edit
RAM usage over 24 hours
The attached image shows increased RAM usage of Akregator over a 24+ hour
window - something w
https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #1 from barray ---
I'm logging the RAM usage every 300 seconds using the SO answer here:
https://unix.stackexchange.com/a/508799
The code is:
```
delay=300
pid="$1"
top -b -d $delay -p $pid | awk -v OFS="," &#x
https://bugs.kde.org/show_bug.cgi?id=440574
barray changed:
What|Removed |Added
CC||bar...@protonmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=440574
Bug ID: 440574
Summary: Memory Leak / Memory Usage For Large Feeds
Product: akregator
Version: 5.16.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severi
10 matches
Mail list logo
