Custom Query (2449 matches)
Results (442 - 444 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2459 | Duplicate | segfault in libcrypto | ||
| Description |
Deluge crashes from time to time. I found the next error in system logs: kernel: [351877.831974] /usr/bin/deluge[30059]: segfault at 7f58729aab80 ip 00007f5867840f5e sp 00007f5847ffd880 error 4 in libcrypto.so.1.0.0[7f586779f000+1ca000] Client Version: 1.3.3 Libtorrent Version: 0.15.10.0 $uname -a Linux XXXX 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux I think this is a regression because a similar bug was discussed on Dec 15, 2012 here: http://forum.deluge-torrent.org/viewtopic.php?f=7&t=41843 |
|||
| #2473 | Duplicate | [Core] Add torrent from url via proxy | ||
| Description |
Something i noticed today is a feature we should add thats new(i think) is the gettting torrent from url should use proxy settings. |
|||
| #2481 | Duplicate | multi-threaded torrent checking | ||
| Description |
from what I can see (please do correct me if I'm wrong and close the ticket), deluge doesn't seem to like using more than one thread to check a torrent even when there are several hundred torrents in the queue. This seems like a waste of resources and time, given that if:the load was spread across more cores, or n torrents could be checked concurrently (where n is the number of threads your CPU supports), or there was a setting to allow you to choose some way to more efficiently use the resources available, Deluge would be several times faster at starting up or adding multiple torrents where the data already exists. tl;dr: spread checking torrents across available cores sorry if this is a little incoherent, I've had a lot of coffee and not much sleep more info on my current system just in case it helps: #deluged --version deluged: 1.3.3 libtorrent: 0.15.10.0 |
|||
