When to call SetProcessWorkingSetSize? (Convincing the memory manager to release the memory)

Question

In a previous post ( My program never releases the memory back. Why? ) I show that FastMM can cache (read as hold for itself) pretty large amounts of memory. If your applica

Answer 1

Problem solved:
I don't need to use SetProcessWorkingSetSize. FastMM will eventually release the RAM.

---

To confirm that this behavior is generated by FastMM (as suggested by Barry Kelly) I crated a second program that allocated A LOT of RAM. As soon as Windows ran out of RAM, my program memory utilization returned to its original value.