There's a specific file, a 5080KB JPEG image, that is acting very oddly. Something about r8848 seems to make this single specific file impossible to download.
It has several sources and downloads, but then usually shows as Completed <blank> instead of Completed Verified, even after the Home tab indicates that all hashing is complete. The file also fails to appear in the download directory; either nothing does, or a file with a short alphanumeric name ending in .tmp and weighing in at 5080KB does. The latter is not, however, the JPEG image, since renaming it to end in .jpg does not result in a file that any image viewer will recognize. (Photoshop, for example, says it's not a JPEG format image and refuses to open it.)
Furthermore the file doesn't disappear from search results (filtered with "Files you have already"). It doesn't do so if the .tmp file is present in the library (presumably because this file does not exactly match the downloaded file -- it's corrupt, also explaining why it won't open in Photoshop).
Last but not least the same remains the case even if the file does show as Completed Verified after download(!).
So, the file is being corrupted on download. Moreover it's corrupted consistently, every single time it's downloaded(!). Moreover it doesn't actually get detected as corrupt, and the TigerTree green bar extends all the way across the file after the download(!!), despite its being corrupt. And last but not least, it sometimes even shows as Verified after download and is STILL corrupt(!!!). And it gets randomly renamed and sometimes deleted on download.
This is NOT simply a case that some joker is sharing a 5 meg file that isn't actually a jpeg (or is a damaged one) with a .jpg name; the weird renamings and deletings couldn't be caused by that.
Moreover it is certainly incorrect behavior on Shareaza's part to a) download a file, b) show a full green TigerTree bar across the bottom when it's done, and c) show Verified in green when the download is done, and yet either d) not put the file exactly as downloaded, bit-for-bit identical, in its library or else e) do so but not subsequently filter it from search results when filtering "Files you have already".
Does anyone know what the hell is going on here? I only see this behavior with a single specific file, which I have "downloaded" at least a dozen times and have yet to actually receive it intact (or even receive a damaged file but one that matches the hash in the thing's URI and so is presumably the file-as-shared).