George wrote:All the memory management changes are now complete, so latest SVN should use a lot less memory when downloading and seeding.

Awesome, I'll give it a go and see how it all goes.

As for my other problem, just to clarify, ktorrent is set to download to /mnt/data/BitTorrent/incomplete and move to /mnt/data/BitTorrent when done. And I have a feeling that the torrents that aren't copying properly now are in ~/data/BitTorrent where data is a symlink to the /mnt/data dir, so things actually resolve to the same dir, but it must be confusing ktorrent, kio, or both. Interestingly the files didn't originally exist in either dir this time around as the entire filesystem was lost, and everything was restarted, so they should have been started in /mnt/data/BitTorrent/incomplete, and it seems they are, as the files do exist in there now after a few tries, but the old torXX links point to ~/data/BitTorrent/filenamehere, which don't exist after ktorrent tries to copy stuff around, and some how the incomplete copy disappears or is truncated after ktorrent sees the ~/data/BitTorrent copy is missing.

At lseast thats how it seems. I can't tell ktorrent to move the data into the right dir, as one or more files in a torrent won't exist where it expects it/them to be, so ktorrent does nothing. Seemingly, in order to fix my issue I need to stop the torrents totally, move the data into /mnt/data/BitTorrent/incomplete, re queue, and do a full data check so ktorrent notices what data may or may not be missing, and stop trying to seed past the end of files, or from non existent files (which causes ktorrent to stop the torrent with an error)., without the data check, ktorrent thinks the torrent is fully seedable, but some of the data is missing (one file out of N).

hope that helps...

George wrote:All the memory management changes are now complete, so latest SVN should use a lot less memory when downloading and seeding.

That is great news. I have always felt that ktorrent could use a lot less memory. After an hour of r856351 testing, it looks stable and OKayish. Memory usage dropped by ~40 MB to 78MB now.

Great! Time for a new release then

The changes are to big for a 3.1.x release, and they need more use and testing in betas and release candidates, so they will only go in 3.2