d3ad social login

[d3ad]

tags labelled 'akregator' e

please login to post
@barray on Mon Sep 20 19:25:06 UTC 2021 said: &e
I'm starting to think my #ubuntu install is now just completely fucked... I've got some pretty bad #ram #leaks going on and things are working less and less efficiently. #akregator and #thunderbird continue to behave screwy. This machine desperately needs to be replaced. I need to get on with developing the #chunkboipro
@barray on Thu Aug 05 06:15:06 UTC 2021 said: &e
Regarding a new #rss #feed #reader to replace #akregator - one of the features I wish they all have is to parse #html (basically a different #xml format) - most #websites that have an RSS button also offer a list of content somewhere, it should be entirely possible to process... I actually don't want a content preview - I just want to know what links are new for the most part.
@barray on Wed Aug 04 23:47:01 UTC 2021 said: &e
@barray on Wed Aug 04 23:38:10 UTC 2021 said: &e
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...
Okay, 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 ...
@barray on Wed Aug 04 23:38:10 UTC 2021 said: &e
@barray on Wed Aug 04 23:35:44 UTC 2021 said: &e
#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.
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: &e
#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.
@barray on Wed Aug 04 20:17:43 UTC 2021 said: &e
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.
@barray on Wed Aug 04 05:51:03 UTC 2021 said: &e
@barray on Tue Aug 03 22:21:31 UTC 2021 said: &e
#akregator is now at *1.6GB* - bare in mind this is just an #rss #feed #reader ! Either it is trying to store *all* content in #ram - or there is a #memoryleak ... I really suspect this is what caused my #laptop to #crash just the other day. I'll attempt to contact them on #irc - but not holding my breath.
Submitted a #bug #report #ticket over at #kde for #akregator https://bugs.kde.org/show_bug.cgi?id=440.. Currently collecting some #data on #ram usage over time, the graph so far looks weird.... We'll see where we're at after 24 hours...
@barray on Tue Aug 03 22:21:31 UTC 2021 said: &e
@barray on Tue Aug 03 05:47:01 UTC 2021 said: &e
#akregator is now at *1.3GB* of #ram ... For all that RAM use it's not even that fast... Bare in mind that its only real job is to fetch an #xml #rss #feed - it doesn't even recover from #reboot very well either (feeds are forgotten). It's impressive that for what should be a simple program, it actually isn't. I'll keep an eye on it... I legitimately could do a better job than this.
#akregator is now at *1.6GB* - bare in mind this is just an #rss #feed #reader ! Either it is trying to store *all* content in #ram - or there is a #memoryleak ... I really suspect this is what caused my #laptop to #crash just the other day. I'll attempt to contact them on #irc - but not holding my breath.
@barray on Tue Aug 03 05:47:01 UTC 2021 said: &e
@barray on Mon Aug 02 21:57:00 UTC 2021 said: &e
I genuinely believe I could do a better job if I built an #rss #feed #reader myself. Do away with the #webengine - get everything out of #ram - build using the principles of #kiss ... It should be using 64MB of RAM, not over 1GB of RAM. Insanity.
#akregator is now at *1.3GB* of #ram ... For all that RAM use it's not even that fast... Bare in mind that its only real job is to fetch an #xml #rss #feed - it doesn't even recover from #reboot very well either (feeds are forgotten). It's impressive that for what should be a simple program, it actually isn't. I'll keep an eye on it... I legitimately could do a better job than this.
@barray on Mon Aug 02 21:46:21 UTC 2021 said: &e
#akregator , the #rss #feed #reader I use is currently using 1.1GB of #ram after just a day... I suspect there might be a #memoryleak or some form of inefficiency here... Is it trying to load *all* of the content actively into RAM? According to this article, apparently it is quite crash prone: https://linuxreviews.org/Akregator Half the problem appears to be the use of the #qtwebengine - it essentially has a whole freaking web browser built in.
@barray on Mon Jul 19 03:58:39 UTC 2021 said: &e
So I have been using #akregator as an #rss #feed #reader for a few weeks now, and generally it is quite good. I do have a few problems with it though. 1. It doesn't support #arrowkeys in the lists, meaning you have to do a *lot* of clicking. 2. If it #crashes or is forced-closed for some reason, it doesn't remember what you have already read. 3. The search feature doesn't allow you to open up an associated feed easily. 4. The import feed should be able to just take a list of #feed #urls - #opml is wonky.
@barray on Sun Jun 27 06:42:15 UTC 2021 said: &e
@barray on Sun Jun 27 06:17:42 UTC 2021 said: &e
Finally finished writing a custom piece of software to abstract the #rss from a corrupted #thunderbird #feed and rebuilding a #opml file that can then be important by another #rssreader - for which I have chosen #akregator for now. What a super pain in the arse that was...
It's really great to have #rss back now, much happier about it. Finally getting news updates again! Fingers crossed #akregator is much better than #thunderbird for #rss ! At least I already exported to #opml file encase I want to go somewhere else, it took an hour or so to rename all of the various #feeds ...
@barray on Sun Jun 27 06:17:42 UTC 2021 said: &e
Finally finished writing a custom piece of software to abstract the #rss from a corrupted #thunderbird #feed and rebuilding a #opml file that can then be important by another #rssreader - for which I have chosen #akregator for now. What a super pain in the arse that was...