Share

Launch4j Executable Wrapper

Tracker: Bugs

5 Using "maxHeapPercent" fails on 32-bit Systems with much Ram - ID: 2832568
Last Update: Tracker Item Submitted ( schlm3 )

On WIndows 32-bit, each process may use a maximum of 2GB Ram
theoretically.
However, the Shadowing of PCI-Adresses consumes some parts of the
Adress-Space and therefore, not the full 2GB of Ram are available for the
Processes.

Therefore, if you have a system with for example 4 GB Ram installed using
Win32, Launch4J fails to start if using
"<maxHeapPercent>90</maxHeapPercent>". Our internal tests with various
systems showed, that you have to use a maximum of "65%" for this setting
such that it runs on all our tested systems.
Notice, that testing this depends on the amount of available memory. So be
sure you test with at least 2GB pyhiscal memory available.

Fix this either by adding a comment in the documentation that explains this
behavior, or by considering that on 32-bit OS'es the maximum memory
available is not 2GB but approx.1.35GB.


Markus Schlegel ( schlm3 ) - 2009-08-05 11:35

5

Open

None

Nobody/Anonymous

None

3.x

Public


Comments

No follow-up comments have been posted.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.