rakshasa/rtorrent — Issue #4: Issues with rtorrent crashing
Author: damorgue
Created: 2011-11-04 22:32:50+00:00
State: open

Below are some problems that I have had since day 1 but never bothered to actually fix. I have decided to update my rTorrent in hopes that it might resolve my issues but I have found nothing on the matter in the change log so I have liittle hope. I am running rtorrent 0.8.6 and libtorrent 0.12.6. I have been running rutorrent 3.0 but updated it to 3.3 yesterday. It is running on a home-built NAS I have direct access to, running 4GB ECC DDR3, a low power dual core, a very fast array (500+ MB/s) and a 90/80Mbit/s connection.
Here are the issues:

rTorrent chrashes and the output below is displayed when to many torrents are added to the watch directory in to short of a time frame (In my case only about 4 torrents can be added before you have to wait a certain time before adding more).

xxx@xxx:~$ rtorrent
Caught Segmentation fault, dumping stack:
0 rtorrent() [0x43b754]
1 rtorrent() [0x43fb27]
2 /lib/libc.so.6(+0x33af0) [0x7ff6f514faf0]
3 /usr/local/lib/libtorrent.so.11(_ZN7torrent9PollEPoll7performEv+0x91) [0x7ff6f66c7f11]
4 rtorrent() [0x47c11b]
5 rtorrent() [0x43bfaa]
6 /lib/libc.so.6(__libc_start_main+0xfd) [0x7ff6f513ac4d]
7 rtorrent() [0x40ea59]
Aborted

Another problem:

rtorrent: DownloadList::confirm_finished(...) download->resume_flags() != ~uint32_t().

rtorrent chrashes and the message above is displayed. This happens if two torrents finish to close to each other and the hash checking fails or if to much hash checking is being made. To many torrents marked as quened also seems to trigger the chrash. Hashchecking seems to go slower and slower until it pretty much halts and crashes.

A third problem

rTorrent runs out of memory and stops some torrents because of it.
ulimit -u returns unlimited
max_memory_usage is set to 3072M (I have tried without the letter suffix and different ranges without result)
rtorrents still won't use much ram at all and claims to run out. I would gladly let it use more.

Some other issues that may be more related to rutorrent than rtorrent:
-It takes about 10-30sec before torrents added to the watchdirectory can be seen in the web ui. Is it watched with some sort of polling and can the interval be decreased?
-Web ui is somewhat slow with many torrents
-Partial downloads are marked as downloading when they are in fact finished
-In the category list, 'finished' includes both 'finished and seeding' as well as 'finished and not seeding'. There is no way to check if they are actually seeding without searching through the list and find them and check their status and icon. Why bunch these categories together under the same icon when they have different statuses and icons in the list?

Does anyone have any help to offer on the matter? I would also very much like if someone could tell me how rtorrent is updated. I would like to keep my settings and session info as well as not have to rehash everything.
Is it enough to make a backup of the sessions and torrents directories and their contents as well as the rtorrent.rc file?
What is neccessary to .configure make and install the unpacked tarballs of rtorrent and libtorrent?
I am somewhat lost here and would greatly appreciate your assistance. Thank you