Opening up new process does not free up the memory of the old process
Hello today I noticed that when you open a new process the Used Memory is not freed. The system monitor shows the old memory and starts consuming memory from the point it left with the old process. So is this really a bug? Or the operational procedure should be close rapidminer everytime and run it again whenever you are desired to start a new process?
Re: Opening up new process does not free up the memory of the old process
RapidMiner frees memory only when it runs out of memory. So when you run a new process, RapidMiner is even supposed to not automatically free memory, but probably only when you run the new process and it starts consuming memory. (as a side-note, there has been a bug that prevents RapidMiner from freeing up memory in some cases, but that has already been fixed and will be included in the next release).