BookScanWizard 2.0 – Memory Management Issues – Leak?
Posted: 25 Sep 2013, 21:24
BookScanWizard is running on a 64bit computer with Windows 7 Pro with 48GB of memory. The versions of Java used were the latest download.
The software was run from a bat file which had this command for the 32bit version of Java.
java -Xmx1280m –jar BookScanWizard.jar
When attempting to run from this command
java -Xmx1536m –jar BookScanWizard.jar
or any larger amounts of memory on the Xmx command, the run fails with this message:
In an attempt to get larger heap space the 64bit version of Java was downloaded. This bat command was executed.
java -Xmx2G -jar -d64 BookScanWizard.jar
and it allowed BookScanWizard to run.
The task here is to create an electronic book which has 353 pages. The input image size is 4896 X 3672.
The processing included only Crop and Perspective and AutoLevels.
Doing batch processing of 10 pages completes, however, any more than 21 pages BookScanWizard halts with this error:
Given that the processing memory demands are page number sensitive it may imply a memory leak.
When running the 32bit version of Java with the Xmx command set at –Xmx1280 it was not possible to get any output from BookScanWizard due to heap errors such as this:
The software was run from a bat file which had this command for the 32bit version of Java.
java -Xmx1280m –jar BookScanWizard.jar
When attempting to run from this command
java -Xmx1536m –jar BookScanWizard.jar
or any larger amounts of memory on the Xmx command, the run fails with this message:
In an attempt to get larger heap space the 64bit version of Java was downloaded. This bat command was executed.
java -Xmx2G -jar -d64 BookScanWizard.jar
and it allowed BookScanWizard to run.
The task here is to create an electronic book which has 353 pages. The input image size is 4896 X 3672.
The processing included only Crop and Perspective and AutoLevels.
Doing batch processing of 10 pages completes, however, any more than 21 pages BookScanWizard halts with this error:
Given that the processing memory demands are page number sensitive it may imply a memory leak.
When running the 32bit version of Java with the Xmx command set at –Xmx1280 it was not possible to get any output from BookScanWizard due to heap errors such as this: