ktorrent – UI Becomes Unresponsive

[RP Charbonneau]

When starting up any torrent the UI for the application will become unresponsive for periods of time. Most of the time the UI will recover from this state, but no crash occurs and there is no trace I can provide at this time. Using the System Activity window to view ktorrents process list will occasionally show that one of the ktorrent process has entered a zombied state. I use KTorrent to seed some ISOs, but if I choose to download something new this issue can make it almost unusable. I'm willing to take any steps as directed to provide some useful information on this bug and will continue to work to track down the issue with maintainers/developers.

[RP Charbonneau (etriaph)]

Apologies, I forgot to mention my platform information. I'm running Kubuntu Wily on an amd64 w/8Gb RAM and 1GB Swap on an SSD and on NVidia GTX 750 GPU with desktop effects enabled.

[RP Charbonneau (etriaph)]

https://forum.kde.org/viewtopic.php?f=235&t=121510

This topic covers this issue. The 1TB SATA HDD I save data to from torrents is attached to the PC using an X-Dock slot; essentially removable media for 3.25" and 2.5" drives. The board they plug into are wired out to the motherboard. See:

Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 795M 9.6M 785M 2% /run
/dev/sda2 119G 105G 13G 90% /
tmpfs 3.9G 18M 3.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda2 119G 105G 13G 90% /home
/dev/sdb1 932G 701G 232G 76% /Storage
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 795M 0 795M 0% /run/user/115
tmpfs 795M 36K 795M 1% /run/user/1000
/home/user/.Private 119G 105G 13G 90% /home/user

The /Storage partition is the location I use when torrenting anything.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

missing information: cat /etc/lsb-release

[Launchpad Janitor (janitor)]

[Expired for ktorrent (Ubuntu) because there has been no activity for 60 days.]

[Martin Rott (burro-bad)]

For me it seems like it's related to this issue:
https://bugs.kde.org/show_bug.cgi?id=354633

(I also confirm similar behavior on Ubuntu 15.10..)