Deluge 1.3.5 reporting false completions

[dasfoo]

Hi,

I recently updated to Client: 1.3.5 and libtorrent: 0.15.10.0. (I previously used 1.3.2, I think; I tried 1.3.4 for a week but got incorrect parameter errors on large files, so I went back to 1.3.2). This is on Windows 7 64-bit.

Ever since installing the latest version, I've been getting random false completions. That is, while many files download correctly the first time, sometimes Deluge will tell me that I have 100% of a file and that it is now seeding. However, I am unable to open some of these files. If I force a recheck on the files that refuse to open, Deluge will then tell me that I didn't really have 100% of the file and proceed to download the rest. Usually the files work after the 2nd 100%, but I will end up having ultimately downloaded considerably more data than the file itself requires.

On one large file, 4.4GB, I ended up having to recheck and download a total of 6.9GB before I had a truly complete file.
On another 6.6GB file, I had to download 11GB for actual completion.

It's not just big files however. I am now doing random checks of all my files at 100%. On one 700.2 MB file I just rechecked, it tells me that I really only have 81.72% of that file.

The only difference from my previous usage in older versions, I think, is that I am using Compact allocation -- which is a new feature,isn't it? This seems like an issue that could be related. I'll switch to Full Allocation and see if it makes a difference.

[Cas]

What filesystem are you using? This sound like corruption of the files on the filesystem because if libtorrent has marked it as complete then all the pieces were correct (hash checked) when downloaded.

There is an issue for uncompleted torrents but I think it is different to what you are reporting.

Compact allocation is an original feature of libtorrent and is actually marked as deprecated.

[dasfoo]

My filesystem is NTFS.

I've gone back a bit rechecking completed torrents. I updated to 1.3.5 on April 9 and the oldest false completions I've found was downloaded on April 12. I haven't found any predating 1.3.5.

[dasfoo]

Update: I have not had this problem with any torrent since switching to Full Allocation. Make of that what you will.