*.ap) left on your disk after running
an apfloat program, it may be because they can't be deleted in garbage collection.
Some JVMs have specific options that must be specified so that a "full" GC is
really done when you call System.gc(), for example with JRockit this
flag is -XXfullsystemgc and with IBM's VM it's -Xcompactexplicitgc.
If you're using Sun's VM you may want to send Sun some feedback regarding bug
4715154
or vote for bug
4171239 or
RFE 4724038.-Xmx1G) or more, running out of address space
may cause further problems. Disk I/O requires mapping files to logical memory addresses. If
the maximum heap size plus the maximum apfloat temporary file size exceeds 1.5 GB you may get
a java.io.IOException: Not enough storage is available to process this command.OutOfMemoryError when the number should be stored in memory. This can happen
because of the heap memory arrangement. The details depend on the garbage collection algorithm
used but often the heap is divided to two "generations" (new and old) and a memory array can
only be allocated from one of these. If the "new generation" is big you won't be able to actually
allocate the whole heap for a single memory array. The solution is to specify a smaller
"new generation" size, e.g. with -Xmn8M or use a different garbage collection
algorithm e.g. with -Xincgc.Last updated: April 4th, 2007