We should separate out the maximum (-Xmx) and initial (-Xms) memory sizes from the "JVM Args for Main JVM" and "JVM Args for Interactions JVM".
This involves making sure that the "JVM Args for Main JVM" and "JVM Args for Interactions JVM" do not contain -Xmx and -Xms arguments, and that the maximum amount is not less than the initial amount.
Then we can respond better to exceptions like
java.lang.OutOfMemoryError and com.sun.jdi.VMOutOfMemoryException and directly suggest increasing the amount of heap space.
Related to
https://sourceforge.net/tracker/?func=detail&atid=438935&aid=1908454&group_id=44253
Logged In: YES
user_id=1075744
Originator: YES
Implemented as of revision r4398 | mgricken | 2008-03-10 19:44:16 -0500 (Mon, 10 Mar 2008) | 8 lines
DrJava now detects OutOfMemoryErrors and VMOutOfMemoryExceptions
inside the slave JVM and suggests to increase the maximum heap
memory. It also detects OutOfMemoryErrors in the main JVM,
initiates garbage collection and attempts to ask the user to
increase the maximum heap size for the main JVM.
Also moved "Save Window Position" and "Reset Window Position"
settings into a sub-pane of "Display" in the "Preferences".