@barray on Wed Aug 04 23:38:10 UTC 2021 said: &eOkay, loading #akregator with #valgrind 's `--track-origins=yes` was unbelievably slow, to the point where the #gui was crashing by just putting a #cursor near it. It's now *barely* usable, but should be just about good enough to use for the #debug ...Good grief programs are bloody slow to start under #valgrind ... Literally takes minutes for #akregator to start! I can see each one of the #rss #feeds being loaded! I hope it is much faster once fully loaded...
@barray on Wed Aug 04 23:35:44 UTC 2021 said: &eGood grief programs are bloody slow to start under #valgrind ... Literally takes minutes for #akregator to start! I can see each one of the #rss #feeds being loaded! I hope it is much faster once fully loaded...#akregator #ram abuse definitely confirmed: https://coffeespace.org.uk/projects/akre.. Next step is to run it using #valgrind and to find out exactly what is actually getting leaked. I'll continue to monitor the RAM too and make sure at least that part is repeatable.
#akregator #ram abuse definitely confirmed: https://coffeespace.org.uk/projects/akre.. Next step is to run it using #valgrind and to find out exactly what is actually getting leaked. I'll continue to monitor the RAM too and make sure at least that part is repeatable.
Still working on the #akregatorramusage problem and have an active #article going on over here: https://coffeespace.org.uk/projects/akre.. The #ram usage of #akregator has swelled from about *1.67GB* to about *1.92GB* in just 21 hours or so. I will post an update soon, but it looks like it could be time to get #valgrind running on this... Something is seriously wrong.