It seems you are running the eazyBI Child process with default settings; is that so?
In larger instances, this is not enough. Increasing the heap memory to 2GB is absolutely necessary, but if your server allows it, you should increase the eazyBI child process JVM heap memory to 4GB (-Xmx4g).
However, if that does not help, please export and send the definition of the failing report to the support e-mail support@eazyBI.com.
The resource requirements highly depend on the dataset and reports used.
Efficient reports based on direct measures coming straight from the database might work with less memory. In contrast, the iterative measures inspecting all issues and relating to historical changes would demand a lot more.
The current general suggestion stands at 4 GB on Jan 2024.
Still - the following factors might increase the memory demand:
multiple simultaneous report executions (>30 report users at once on the same node)
high-volume data cubes (>2GB per data cube)
excessive background datasets due to multiple dimensions on rows (like 3 or more high volume dimensions, each having 500+ members)
It is possible to create a report that consumes almost any amount of memory, but that is not a goal to strive for.
If you start seeing out-of-memory errors - you might not have allocated enough or you might use it more efficiently.