I already tried that, mate and to no avail, if my client is seeding for a period of ... dunno at least 10-20 minutes to even hours, eventually it will start chokin' my ram to the sky (at least a good hour of seeding to actually see a big difference in memory utilization). @dreadedwingknight, I've disabled both cache options in the client prior to this version (now there's a new update, 30260 i'll test on that). Also if u think windows cache system behaviour is herratic and in this case, on latest 3.3.2 client, it's hogging my memory, then why on earth 3.2.3 is NOT having this problem, with or without cache (write/read) enabled ?