Deluge
Custom Query (2449 matches)
Results (142 - 144 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3167 | Fixed | tracker_icons.py does not clean up /tmp entries from failed hosts | rexar | |
| Description |
If Deluge attempts to obtain a tracker icon for a tracker that is unreachable, or has a re-direct to self (perpetual HTTP 301/302) the errorback routines in tracker_icons.py do not have access to the temporary filehandles / paths created as part of the download_page method, and as such is unable to clean up these pre-allocated resources. Over a period of time under Linux, this fills the /tmp directory with a large amount of junk files in the form of deluge_ticon.xxxxx Attached is a workaround targetting the 1.3.15 release version of tracker_icons.py which allows the errorback routines to clean files allocated from failed attempts. This was developed against my scenario which is the GTK client connecting to a remote server, it hasn't been tested for other use cases. |
|||
| #3164 | Invalid | migration | dar54 | |
| Description |
I have attempted to migrate utorrents to Deluge several times without success. utorrents is not listed among plugins. I use the most recent version of Firefox. Please help. |
|||
| #3159 | WontFix | Random crashes (could be realted to libtorrent alerts code) | rbogorodskiy | |
| Description |
Deluge crashes randomly, most often it happens right after start. While crashing, python dumps a core. Initially, I reported that to libtorrent: https://github.com/arvidn/libtorrent/issues/2779 (this contains more details about software versions, includes a backtrace from lldb etc). I was told that it's quite likely a bug in Deluge caused by alerts-related code change in libtorrent 1.1.0. Direct link to a comment with explanation: https://github.com/arvidn/libtorrent/issues/2779#issuecomment-364646798 |
|||
