Files downloads but bad pieces discovered on recheck.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download completes 100% and begins seeding
2. Click recheck
3. Remaining 1-2% bad pieces begin downloading
4. Sometimes repeat steps a few times to get uncorrupted download. 

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Deluge 1.3.10 on Windows XP Pro x64 (Build 3790 service pack 2)
libtorrent 0.16.18.0

Please provide any additional information below.

Sometimes Deluge will complete a torrent and begin seeding, however the file 
has corrupt pieces which will redownload on a forced file "recheck". Sometimes 
this recheck needs to be performed several times to get the last 1 or 2% of 
valid data.

It seems to occur on files around 1GB+, but I've only been a Deluge user for a 
couple of months, so I haven't extensive experience.

This bug has been brought up in Deluge ticket system 5 years and then 3 years 
ago but was closed without action. Deluge suggested the problem was in 
libtorrent and that a ticket should be opened with libtorrent instead

Refer to closed (wontfix) Deluge ticket http://dev.deluge-torrent.org/ticket/604

Original issue reported on code.google.com by mathew.g...@gmail.com on 2 Nov 2014 at 2:19

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Bad RAM stick. Have to take out the faulty RAM chip. There's no way to tell 
which stick just keep testing with 3 out of 4 RAM chips installed until the 
problem is solved.

Original comment by j0shi3s...@gmail.com on 4 Dec 2014 at 6:22

[GoogleCodeExporter]

I'm having this problem all the time, deluge from git and 
net-libs/rb_libtorrent-0.16.10 under gentoo linux. RAM is unlikely to blame as 
I have transmission on the same box which does not have the issue.

Original comment by non7top on 14 Dec 2014 at 2:34