Jump to content

RSS feed constantly restarts completed downloads


Tufflaw

Recommended Posts

I saw some old posts on this issue but it was never really resolved (and only involved mininova).

I have a bunch of feeds from Bitsnoop and EZrss that were all set up the same way (do not automatically download all items).

RSS downloader for all the feeds is simple:

rss.jpg

When I first added the feeds, all the shows in them all showed up and started downloading (several thousand) - so I removed them all, and all the statuses show as "previously downloaded". However, every so often, large groups of the shows just start downloading automatically for no apparent reason.

I've also noticed if a click on the feed name and Edit Feed, it automatically starts downloading ALL the shows in that feed again.

I'm running 2.2 on Win 7 - any suggestions? Thanks!

Link to comment
Share on other sites

  • 2 weeks later...

That option does something different.

I think I know what's going on here, though. By editing the feed, uT now thinks it's a different feed, so it clears out the history for it and starts downloading everything because you created a filter * to download all torrents. I guess the only problem is that uT shouldn't do that unless the URL actually changed.

Link to comment
Share on other sites

Ah, I see. The items are not expected to be downloaded because they have already been downloaded once.

Looking at the code, there's a limit on the rss history set to 600, and it's applied in a somewhat odd way:

Every time a new item is added to the history (i.e. we download a torrent from a feed) if the history has more than or equal to 600 items in it, we clear out the 100 oldest ones.

This would explain that items would start to download in chunks. I would assume the idea here is that you wouldn't have thousands of rss items. This doesn't seem to be a regression, so I may be inclined to bump a fix for this to 3.0. A short term fix would be to increase the limit to 1200 or so.

Link to comment
Share on other sites

Ah, I see. The items are not expected to be downloaded because they have already been downloaded once.

Looking at the code, there's a limit on the rss history set to 600, and it's applied in a somewhat odd way:

Every time a new item is added to the history (i.e. we download a torrent from a feed) if the history has more than or equal to 600 items in it, we clear out the 100 oldest ones.

This would explain that items would start to download in chunks. I would assume the idea here is that you wouldn't have thousands of rss items. This doesn't seem to be a regression, so I may be inclined to bump a fix for this to 3.0. A short term fix would be to increase the limit to 1200 or so.

Excellent, thanks for the response - at least I'm not crazy :)

Link to comment
Share on other sites

  • 4 weeks later...
  • 2 weeks later...

You guys seriously need to fix this ASAP. I woke up this morning to find that a torrent that had 30 minutes left to download (which I set uTorrent to shutdown on finishing) was paused by several seasons of the office, mad men, entourage, etc. now seeding!!! Pls help Is there a way for me to increase this limit at least?

Link to comment
Share on other sites

  • 2 weeks later...

So I'm having this same basic problem.

I have maybe 30 feeds. Occasionally, it just randomly starts re-downloading all the files from the feed even if they were marked as 'downloaded' already.

These feeds only provide the most recent 30 - so its not like there is a huge list of 600 torrents in the RSS feed.

Link to comment
Share on other sites

This EXACT thing happens to me about once every month (just happened last night). I have 21 RSS feeds, most of which are dormant (still, 12-30 torrents are listed in the RSS at any given time). Seems like, randomly, uTorrent decides to re-add everything, and being limited to a 600 torrent history seems like it could be the problem ESPECIALLY if it counts normal torrents as part of that 600. It's a HUGE problem for me because I can download at 4MB/s ... when uTorrent decides to do this, my HDD space (and monthly bandwidth) starts getting eaten up REAL fast. I usually catch it when my router IMs me that someone is using a ton of bandwidth ... that's after 25GB has been used in a 24 hour period.

In my case, I move old series' to another drive for archiving (and I rename them) so, when uTorrent re-adds everything, uTorrent can't find stuff older than the current season and it's re-download time; this cycle doesn't end until all the RSS torrents are re-downloaded and stored.

If it's as simple as that 600 history, can we increase that through an advanced setting or something? I'd change it to 10,000 without issue (on my personal system, lots of resources) ... I just REALLY don't want this to happen ESPECIALLY now that I am planning to add another ~10 feeds and, seemingly, it would bring my "current torrents in RSS" to well over that 600. I counted them, at present, my RSS feeds total 553 torrents listings/torrents.

These feeds only provide the most recent 30 - so its not like there is a huge list of 600 torrents in the RSS feed.

30 feeds, 30 torrents each ... 900 listed torrents. To me, it sounds like you should be in perpetual re-downloading if this limit is actually 600.

Link to comment
Share on other sites

Yea - this is rediculous.

Any chance we can get a temporary fix? Even the line in the sourcecode (linux!) that I can change this myself on then recompile would be great.

FYI, i have this same exact problem in both windows and linux with the current released builds for both.

Link to comment
Share on other sites

Could arvid please implement the fix he spoke of 2 months ago? If you just made a single beta build with this fix, I'd be happy and not upgrade again until 3.0 where this problem would ideally be fixed / have a solution (advanced setting).

I am really surprised there aren't more people with this problem; the way I use RSS (auto-downloading recurring series' episodes) is probably the same way almost everyone that uses the RSS feed option uses it ... I guess not too many people track as many shows as I do.

Considering arvid figured out exactly what it is that causes the issue, and it seems pretty simple to put an advanced option to fix, seems like a no-brainer to implement into the client. As a ghetto fix, I'd be content with a hex location in the file I could find-replace to increase the number (plus, possibly, a max I could increase it to before it breaks the purging code), I'd be OK with that as well.

Link to comment
Share on other sites

  • 2 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...