Interesting, it seems like #linux and #unix really do not handle large numbers of #file or #directories gracefully: http://be-n.com/spw/you-can-list-a-milli.. A #hackernews #comment points out that you get some #memoryleak like behaviour if you put too many files into a directory: https://news.ycombinator.com/item?id=281.. Seems to me as if the #ext #developers should have implemented #autoshrink anyway for completeness - this will only ever create #bugs ...
@barray on Tue Aug 03 05:47:01 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.#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 , 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.