these best describe my feelings about this thread:
once again I'll reiterate....the problem was / is NOT a program with a memory leak
it was because windows index service had memory allocated for it that it was no longer using
the reason it had so much allocated is because it just ran through ~2 million files rebuilding the index
somehow windows (or indexing itself) decided because of this that it still needed a bunch of ram allocated
thnx for the info MilesAhead, that all seems to make sense!
yeah. the apps that need it will just ask for it again, but the apps that really don't need it and have a bunch allocated....it'll solve that issue. which is exactly what I was wanting.
I have pretty much the same things open now as I did then and I have ~2.5GB of free ram (this is without doing anything with the cleanmem). I did NOT have too many things open. also you have kb confused with MB for the FF and winamp use.