Standard Java Virtual Machine parameters can be passed through the configuration file
${certivity_home}/etc/certivity.conf(.sh)
in the default_options
property by pre-pending -J
to the standard parameter, for example
-J-Xmx256m
.
If you handle larger files (especially the PDF operations are memory
consuming) or more files at the same time you may ran out of JVM Heap
memory. By default CERTivity comes with a maximum of 256 MB configured as
above. Depending on the memory available on the target machine, the
operating system 32/64-bit architecture, you can specify different sizes
for memory, for example by modifying -J-Xmx256m
into
-J-Xmx512m
. After doing this setting you need to restart the
application. If the heap memory amount that you specified is too high for
that platform/32-bit model, upon starting up a "JVM
creation failed
" message will be present. You will need
to adjust the memory settings according to your architecture - for example
on Windows on 32-bit JVM distributions due to the 32-bit Windows process
model you cannot specify values larger than about 1100 MB. It is also not
recommended to set the maximum JVM heap to be larger than the physical
memory.
Note that this file is specific to each CERTivity version, so this allows you to manage each version independently.
CERTivity has a Memory Detection system letting you know when the
maximum heap memory passes a threshold. This is configured in the
Application Options (accessible through Tools>Options
panel as described in the section called “Tools Menu”) by the
property Memory usage warning max threshold, which comes with the default
value of 90%. In such case the following dialog will be presented:
It is possible that after this warning the JVM may issue an OutOfmemory error if the threshold is too tight. In such a case please adjust the JVM heap setting as described above.
The CERTivity application also features a memory toolbar, which by default is on - there you could see the exact memory used and even force a garbage collection.