This screen allows you to configure the JVM options used when starting ZAP.
A free format text field which will be added to the Java command line call when invoking ZAP via either zap.sh or zap.bat.
The option was added so that the Java maximum memory allocation pool size can be set,
which is of the form: -Xmxn where n is the size in bytes.
Good values for this field could be:
Unlike the other ZAP options these are held in the file
.ZAP_JVM.properties in the user’s default ZAP directory,
which depends on the OS being used, for example:
If you make a mistake when setting these options then ZAP may fail to start.
If that happens then deleting this file should fix the problem.
Windows Notes: These options are not used when starting ZAP via the executable. The directory where the file
.ZAP_JVM.properties is located depends on the environment variable
The lower portion of the dialog displays details of the current JVM memory configuration. Including:
The values are displayed in human readable IEC units based on base 2 calculation (for example: 1024Bytes equals 1KiB, etc).
Generally max should be close to -Xmx (if specified). However, the following behavior was observed during testing under Java 8 on Windows OS.
-Xmx512m was specified (which should calculate out to ~488MiB), however, 455.5MiB was displayed.
-Xms512m -Xmx512m was specified, however, 475MiB was displayed.
-XX:+AlwaysPreTouch -Xms512m -Xmx512m, and 474.5MiB was displayed.
So it seems the JVM does some calculation/manipulation at execution which may mean that the results may not align as expected for the options the user inputs (this is a JVM issue, not a ZAP issue).
|UI Overview||for an overview of the user interface|
|Options dialogs||for details of the other Options dialog screens|
|Java 8 options|