https://bugs.launchpad.net/ubuntu/+sour ... bug/189691

This kind of bug has been described before in our forums here, that a torrent with a huge number of files might cause the ulimit to be exceeded, and I believe our previous concensus was to have KTorrent respect the ulimit set by the system by keeping itself to only that many active file handles at a time.


I know at the time already that development was focused at KDE4, so I think it's a good idea for us to get this handled with ktorrent KDE4.

socket leak has already been fixed for 3.0. iirc, first commit after 3.0rc1

Indeed a socket descriptor leak was fixed right after the release of 3.0rc1

(see http://bugs.kde.org/show_bug.cgi?id=156163)

So this is most likely the cause of your bug. Seeing that problems with to many files open have become quite rare on the KDE3 version.

What about for cases where I actually have a torrent with 5000 files in it?

jdong wrote:What about for cases where I actually have a torrent with 5000 files in it?

We only open files when they are necessary, and when we do approach the limit we will switch to buffered mode for chunks, normally we use mmap (which requires the files to be open).

With buffered mode we will open the file for a short while and then do our stuff (reading or writing a chunk), and then close it again.