Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1038 Liferea Pulls Continuous Updates from TT-RSS

v1.8
closed-fixed
Lars Windolf
Networking (27)
7
2013-07-22
2012-11-01
Nathan Acks
No

When setting up a TT-RSS source, Liferea pulls continuous updates, downloading all of the feed data and then immediately downloading the data again. This cycle will continue until Liferea is closed, causing high load on the TT-RSS instance, and will immediately resume when Liferea is restarted. While this issue causes no noticable problems in Liferea's UI, if running TT-RSS on a small server it can cause enough server-side load to interfere with other webapps.

I see this behavior with both Liferea 1.8.7 and 1.8.10, both using TT-RSS 1.6.0 as a back end. However, this post from the liferea-devel mailing list seems to indicate that the issue has been present since at least Liferea 1.8.0 and TT-RSS 1.5.7: http://sourceforge.net/mailarchive/forum.php?thread_name=4F01473E.8060803%40exyr.org&forum_name=liferea-devel

A lightly sanitized log produced using liferea --debug-all is attached.

Discussion

1 2 > >> (Page 1 of 2)
  • Nathan Acks
    Nathan Acks
    2012-11-01

     
    Attachments
  • Walter Bell
    Walter Bell
    2013-02-24

    I'm seeing the same issue in 1.8. Here's a patch to fix the issue-- from looking at other sources, the ttrss source doesn't enforce an update interval.

     
  • mossroy
    mossroy
    2013-03-24

    I also face the same issue.
    My tt-rss 1.7.5 instance is installed on a sheevaplug server (1.2 GHz ARM single core)
    If I start Liferea, the server's CPU reaches 100% and does not go below until Liferea is shut down.

     
  • I am also seeing this under 1.10-rc1. The patch doesn't apply cleanly so here's a new one that seems to work.

    As well as this, I am seeing a massive memory leak when using tt-rss under both 1.8.12 and 1.10-rc1. At one point, it was using over 2GB. I'm not sure if it's related but I will monitor the RAM usage now that this patch has been applied. However, I suspect the problem will simply take much much longer to appear now that it's no longer checking continuously.

     
  • mase76
    mase76
    2013-05-07

    The patch did not solve it for me.

     
  • James' patch works well for me, although it seems he forgot to include a #define of TTRSS_SOURCE_UPDATE_INTERVAL. Here's a git format-patch formatted patch against git commit 845cbdfd63512b5b2afa0b7551f3ee8981479695 with the define included.

    This code might need a more thorough review, but I'm hoping a working fix for this rather serious bug can be added soon.

     
  • Actually that line is already present in the 1.10-rc1 tarball but it was removed in commit 868e8187bde1a12f915e70b4f706f6adbcffdc54 because it is apparently useless!

     
  • James, aha!

     
  • mase76
    mase76
    2013-05-08

    I patched against the Debian Package of 1.10rc1.
    It seems to work, but the update message in the status
    bar does not disappear every time. But I did not see
    related traffic with wireshark.

     
1 2 > >> (Page 1 of 2)