Using the same VM to compile multiple java files eventually leads to an OutOfMemory Exception being thrown.

Problem first appeared in b70 jdk beta_refresh build and does exist in b71 and b72 as well.

Attached to this bug report is a tar file. It contains a shell script called runme.sh, a java soure file called memleak.java and corresponding class file. To recreate this problem, run the shell script. The shell script invokes the memleak class which iterates through an invokation of com.sun.tools.javac.Main.compile on the memleak source file.

Usage for the script is as follows:

runme.sh ${JDKBUILDID} ${ITERATIONS}

where ${JDKBUILDID} should be replaced by the BuildID for the JDK you want to test and ${ITERATIONS} is the number of compilation iterations you want memleak to run. Setting ${JDKBUILDID} to any build ID greater than b70 and the ITTERATION value to 100 seems to consistently create the problem. If you specify b69 build ID, problem does to appear