> I ran it for 2 days with exactly 3 non-public torrents. At the time
> I shut it down, this was the memory usage:
>
> dilinger 13592 2.3 11.8 321624 116036 pts/1 Sl+ Nov05 66:39
> /usr/bin/valgrind.bin --leak-check=full transmission
Unfortunately, you didn't reproduce the issue in this case. (Recall
that valgrind multiplies memory consumption by 3.)
> ==13592== definitely lost: 6,432 bytes in 21 blocks
> ==13592== indirectly lost: 19,396 bytes in 969 blocks
> ==13592== possibly lost: 2,624,838 bytes in 39,620 blocks
See?
Juliusz
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
