On Sun, Oct 16, 2005 at 05:23:01PM -0400, Greg Wooledge wrote: > Package: rtorrent > Version: 0.3.4-1 > Severity: normal > > > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > greg 15173 21.6 0.7 6484 3816 pts/10 S+ 14:48 1:07 rtorrent > greg 15173 6.5 1.6 18904 8552 pts/10 S+ 14:48 1:08 rtorrent > greg 15173 4.6 2.8 33240 14668 pts/10 S+ 14:48 1:08 rtorrent > [...] > greg 15173 1.2 26.0 219764 134324 pts/10 S+ 14:48 1:46 rtorrent > > > That's all just downloading a single torrent file. > > * Star Wars Revelations > * Torrent: 3292.9 / 7951.3 MB Rate: 9.3 / 31.5 KB Uploaded: 76.3 MB > * > > I had to restart rtorrent twice because it kept blowing up with an error > message about failure to allocate memory (presumably because it hit my > ulimit). I originally intended to wait until the error appeared again so > I could include it in the bug report, but I ran out of patience. (Also, > I've raised the ulimit for this third run.) > > Not sure whether it matters, but I've got max_peers = 10 in my .rtorrent.rc > file -- but for this specific file, I raised max_peers to 40 by pressing '6' > a few times on the file's download-detail screen. > > $ grep '^[^#]' ~/.rtorrent.rc > min_peers = 10 > max_peers = 10 > max_uploads = 5 > upload_rate = 10 > port_range = 6881-6889 >
Hi, Many thanks for the bug report. This looks like an upstream problem. Before I forward this to the upstream author, can you confirm whether this problem still exists in the latest version (0.3.6-1)? Many thanks, Qingning
signature.asc
Description: Digital signature
