copy of post to abc forum:
Hi Tim,
I have attached (email) some more pics showing ram usage in abc.
abc_ram20.bmp is after abc run all night SEEDING three torrents only (i.e., no d/l)
abc_ram21.bmp is several minutes after place all three on pause and then CLOSE (exit) abc (note NO CHANGE)
abc_ram22.bmp is after KILL process "TREE" in task mgr EACH on four instance of abc found running.
three instance were use about 3m ram, 1 instance was use about 55m ram
*** THIS PROBABLY NORMAL ***
>>>> <<<<
>>>> BUT <<<<
NOTE in abc_ram22.bmp FOUR HUGE DROP in ram usage chart as each process in turn is killed off.
AND note the "commit charge" DROP from about 650m to about 200m.
IS THIS NORMAL ??? For program to suck up 450m of (swapfile) ram?? just for UPLOADS !!!!
If program in FACT NEEDS to have lots of ram/swapfile to track lots of file pieces being uploaded efficiently that is fine of course.
BUT, we end users of this wonderful BT client of yours would like to know this so we dont tear our hair out perplexing
over why this happens.
..........
Thanks for your good works Tim.
Alfred