Custom Query (2449 matches)

When GTK is iconofied on ubuntu 16.04 and a torrent is finished, if you open the GTK interface by double click on the icon, it will not say that it's completed but still says that it's downloading. using the deluge-console shows as completed. have to close deluge and open it again then will show the files completed or not. when not iconified all ok.

While adding a torrent using a command similar to this:

deluge-console add -p 'C:\Path\With Spaces' D:\my_torrent_file.torrent

, if what the torrent downloads contains folders, the download path will be something like this:

C:\\Path\\With Spaces\\torrent_folder\torrent_file.txt

And that single slash ("\") is inconsistent with the others, therefore, deluge returns the error

The filename, directory name, or volume label syntax is incorrect: C:\\Path\\With Spaces\\torrent_folder\torrent_file.txt

Paths containing no white spaces, or torrents that do not have a folder in their download do not have this issue.

Image: ​http://i.imgur.com/m5g77nv.png

While seeding/downloading a large number of torrents (~200, but issue starts appearing with much fewer torrents), upload and download speed drops to 0 every time Deluge is generating resume data, which happens every 3-4 minutes. After resume data for all torrents is generated, speed picks back up slowly as it looks like it has to reconnect to all peers, only to happen again a few minutes later.

The logs contain the following data for every torrent file:

[DEBUG   ] 20:35:42 alertmanager:123 save_resume_data_alert: torrent_name1 resume data generated
[DEBUG   ] 20:35:42 alertmanager:123 save_resume_data_alert: torrent_name2 resume data generated
[DEBUG   ] 20:35:42 alertmanager:123 save_resume_data_alert: torrent_name3 resume data generated
[DEBUG   ] 20:35:42 torrentmanager:1106 on_alert_save_resume_data
[DEBUG   ] 20:35:42 torrentmanager:1106 on_alert_save_resume_data
[DEBUG   ] 20:35:42 torrentmanager:1106 on_alert_save_resume_data

And it goes on like this for all torrents which takes ~10 seconds, then transfer speeds start going back up.

Here is an example speed graph (5 sec update frequency):