Custom Query (2447 matches)
Results (403 - 405 of 2447)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1287 | Fixed | High CPU I/O Wait Usage | ||
| Description |
Deluge 1.2.3 high CPU IO usage. CPU IO usage goes up to 50% usage (one whole core!). Even when the client is doing virtually nothing (not downloading, only 30 actively uploading) Deluge CPU usage is LOW 15-20%~ CPU IO usage is disproportionately high. Hardware: Intel Core 2 Duo E7400 @ 2.8GHz | 2GB RAM | 2*500GB RAID 0 (soft) Software Versions: Debian 5.0" | Deluge 1.2.3 | Libtorrent rasterbar 0.14.10-2 | pygtkmvc 1.99.0-1 Deluge Settings: bandwidth- http://i187.photobucket.com/albums/x268/antdgar/Picture20-2.png cache- http://i187.photobucket.com/albums/x268/antdgar/Picture19-2.png number of torrents- http://i187.photobucket.com/albums/x268/antdgar/Picture21-3.png |
|||
| #1904 | Invalid | WEBUI doesn't connect to deluge-daemon after refresh (F5) | ||
| Description |
After reboot the possibility to connect Deluge: Web UI tot Deluge-Daemon is gone if you press F5 or just refresh button on your browser. The only way to see the torrents, is to open GTK and connect to the deluge-daemon. |
|||
| #2451 | WontFix | Deluge crashes after 10-210 Minutes | ||
| Description |
Deluge crashes after a rather short period of time 10-30 on Windows 7 x64. Windows says libglib-2.0-0.dll is the cause This happens only when an torrent is active and the time before crashing takes longer on deluge-debug.exe than on deluge.exe |
|||
