This content has been marked as final. Show 3 replies
That's expected and documented behavior that exists for very valid reasons. If you really must know the how and why, there is plenty of information available like this whitepaper:
Remember: the JVM is a virtual machine which deals with its own memory management. The last thing you want to do is mess with it.
902020 wrote:All modern desktops use virtual memory. That is a feature of the OS which impacts all normal applications including Java VMs.
... and that it should release it for other application ?
Some features of virtual memory.
1. Applications have their own addressable memory which is not impacted by other application (normal) usage.
2. Memory that is reserved by an application which is not being actively used does not impact other applications.
How can I be sure after a memory consuming task that the JVM won't keep the memory for itselfYou can't, because it will.
This only costs you disk space.