When I select to delete a torrent and its data, the UI can freeze while the OS is busy reclaiming tons of inodes or whatever it's doing. Could this be moved off the main GUI thread? Either move it to some thread pool, or use libaio or some such to do it asynchronously (I'm guessing the former is easier).

It's not a huge deal, it's just spit-n-polish at this point

(Running KTorrent from git - reporting as 4.2-dev, last checked for new code a few days ago.)

Thanks,

The deletion of the files is done in the background (using KIO), so it must be the directory tree cleanup.

I'm just confused as to why that would freeze the UI. If it were really done in the background, the UI shouldn't freeze.

The directory tree cleanup isn't done in the background.

Must be a problem for big trees.

Could this be moved to a background (non-UI) thread?

In my case, the torrents are held on an external USB disk, and that disk has nearly nothing else on it. This disk spins down frequently as it's rarely in use. For the most part, this is sufficient. It means that it takes a bit longer to use the downloaded material, but generally that's fine.

However, it's not just the spin-down, as I have deleted torrents while downloading new ones, and I notice my network usage drop to near zero(*) for a few seconds (using conky to monitor) while ktorrent's UI freezes, and then ktorrent seems to need to renegotiate before my network usage gets back to "normal" for the current torrent.

(*) other apps continue to function, so if I'm browsing the web the network doesn't necessarily go to actual zero.

I will move it to the background for 4.2.