Issues with rtorrent crashing

[damorgue]

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

(Second problem was resolved)

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? -resolved, although it still sometimes takes longer that the specified number of seconds
-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?

Edit: rtorrent and libtorrent have been updated to 0.8.9 and 0.12.9 respektively and the problems remain, the main one being the first one regarding segmentation fault.

[rakshasa]

Don't use such an old version of the client.

Also linux does not report how much mapped memory a program uses.

[damorgue]

None of the problems seems to be mentioned in the changelog though.

It shows how much memory is used in total in the second row of the output of 'free -t -m'. In total, my system uses 1GB when rtorrent seems to run out. There is 3GB more for it to use that is just caching done by linux when it has spare memory as usual.

Also, any help in the upgrading part? The guide on your page hasn't been updated since your switch to git. There is very little info on upgrading. I would simply like to know what files to remove or keep backups of and if there is anything special needed to be done beforehand, and if unpacking, configure, make and install is enough?

Thanks for the fast respone anyway.

[damorgue]

I am now using 0.8.9 and 0.12.9 and the only problem that was resolved was the race condition when a torrent finishes while another one is hashing. The others still happen every single time.

[mytskine]

@damorgue: I believe you should compile libtorrent and rtorrent with debug symbols. Without this a backtrace is useless.

[rakshasa]

Also the current release version is old, so only bug reports against git will be useful.

In addition max_memory_usage does not do what you seem to think it does, as it indicates the address space not physical memory limit.

[damorgue]

Here is the deal, I believe there is not bug. I believe I make some sort of mistake during installation that I just can't find. I am running a fairly standard setup with ubuntu 10.04 and someone should have noticed this it before me. Odds are it is just me, although I have installed it some 20 times in the past week with different packages and settings. I get no errors however and I guess there should be some kind of error if not all of the required dependencies are installed. There are quite a few different sources on how to install rtorrent and I would really appreciate some pointers.

-If I were to install rtorrent 00a4235 and libtorrent ba24b8e from here, what are the dependencies, all of them?

-Do I just add the following to the makefile:
CC= -ggdb
CFLAGS= -ggdb
CXXFLAGS= -ggdb

-Should I disable cplusplus or not when installing xmlrpc-c?
'./configure --disable-cplusplus'

-Should I use '--with-xmlrpc-c'?

-Some people leave out './autogen.sh', how big of a difference does it make? I have always assumed that it is required but some guides omit it.

-Do any of the dependencies clash with others, because I may during my testing have installed several closely related packages?

EDIT: -I installed rtorrent 00a4235 and libtorrent ba24b8e and it resisted the initial bursts of 5-10 torrents at a time without crashing. i will return once I try to load a larger amount at the same time. Seems good so far though.