I\'ve create a c# application which uses up 150mb of memory (private bytes), mainly due to a big dictionary:
Dictionary Txns = new Diction
Windows has two memory availability events. I'd expect the CLR to respond to this. If there's plenty of memory available, the smart thing is to NOT run the garbage collector. So, to make sure that you are indeed observing bad CLR behavior, please repeat this test with another dummy application using a big heap of memory.