3 Replies Latest reply on Dec 14, 2011 12:56 AM by EJP

    JVM not releasing memory back after consuming

      We have an application which use about 150m on heap after startup,
      but some task can make the memory grow up to 700m.
      The problem is that after the "memory consuming" task, the JVM don't release it.

      So, here is my question : How can I be sure after a memory consuming task that the JVM won't keep the memory for itself when
      the really used memory is about 150m and the allocated size is about 1gb ? is there any clean way to notify the JVM that this memory usage was really
      temporary and that it should release it for other application ?