Knowledge base:
Configuring the GUI to Use More Memory
Posted by Mathieu Strubbe, Last modified by Craig Godbold on 09 August 2023 02:28 PM

The ByteBlower GUI is a java application, which means that it uses a certain amount of heap space.
Heap space is used for the dynamic memory allocation of Java objects and JRE classes at runtime.

In the ByteBlower.ini file, which is located next to the executable file, the heap size preferences can be configured.


Currently these are the default values used by 32-bit ByteBlower GUIs:

This means that a maximum of 1024 MB will be used as heap space. 
That should be sufficient while working on most projects, but when working with big projects, generating big reports, memory problems may occur.

On a 32-bit platform, the maximum theoretical heap limit is 4G.
Due to various additional constraints such as available swap, kernel address space usage, memory fragmentation, and VM overhead, in practice the limit can be much lower.
On most modern 32-bit Windows systems the maximum heap size will range from 1.4G to 1.6G.


The 64-bit GUI can allocate much more memory.
These settings are used by default:

This means that initially the GUI will start with 512 MB, which can grow up to a maximum of 2048 MB.

We experienced that these are good default values, but of course you may require different settings.

Contact us at if you'd like assistance! 

(0 vote(s))
Not helpful

Comments (0)

We to help you!