Hi,
I think in this thread there are described several problems.
If I start rapid miner, run any process, and leave rapid miner running I see the memory used by javaw.exe slowly growing.
This does probably no harm, RapidMiner just does some background calculations (e.g. updating the memory monitor

), and since it does not need the memory the garbage collection is not triggered. As soon as the memory is needed, it will be cleared.
To the Rapid Miner development team:
There is a very serious memory leak in Version 5.1. I am reading a large (900,000 rows) csv file in. The system monitor shows memory usage slowly increasing, as expected. But when the process finishes, and a new process is started, the memory usage starts at the same level where it was when the first process ended- the 2nd process then crashes due to lack of memory!
I have tested this with the Windows performance monitor as well- which confirmed that the memory was not being released when the pocess ended.
Just a guess: did you leave the results view open? For that, the data also stays in memory.
I am using the "Free Memory" operator- which seems to have no effect.
The Free Memory operator only triggers the garbage collection explicitly, which frees data which is not needed for anything. That could speed up things later, but it does not free any memory which would not be freed automatically. Thus it won't solve any out-of-memory problems
The only way to run the 2nd process is to restart Rapid Miner!
Please try to close the result tab before running the second process. If that helps, we are done, if not, we will have a look at it.
my central memory space is 8GB and no other applications are running, the Xms parameter for Java is set at 6GB.........

Please check that RapidMiner can really access that much memory. If not, please try the Xmx option instead of Xms.
@all: please let us know if your problems persist.
Best,
Marius