The second problem is that my torrents go into "error" status when I download them directly to a Samba share running off a Linux box. I do not seem to have this problem when using smaller torrents (200-300 MB). I'm guessing that this extra memory is being used as some kind of disc cache, and it is not being de-allocated correctly, but that's just my guess. The rate at which I run out of memory seems to correspond to the overall size of all the torrents I'm downloading, so if I am downloading many large torrents, it only takes an hour or so to run out of memory. Likewise, this huge amount of memory does not seem to be allocated to any of the processes shown in task manager, which should take less than 1 GB of physical memory in total. However, this is the overall memory usage of my machine, not of deluge.exe or deluged.exe (they only take about 90 MB). When using Deluge v1.1.9 on with large torrents (single files larger > 5 GB), my memory usage slowly increases until I have no physical memory left, according to task manager. I have 4 GB of physical memory and another 4 GB of virtual memory, and I'm running Vista 64. Two problems occur when I download large files using Deluge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |