We have a crosstab report with ~7200 rows. Each row has icon conditional formatting which results in over 5MB .pdf file when exported. In web it works as expected, but exports cause insufficient memory issue which crashes Yellowfin environment:
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00007fb605f81000, 12288, 0) failed; error='Cannot allocate memory' (errno=12)
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 12288 bytes for committing reserved memory.
# An error report file with more information is saved as:
Are there any settings we can define to avoid this? Do you have any suggestions how to work around this?
Thank you for your help,
Sorry to see that you are running into issues while attempting to export this large cross-tab report.
What version of Java are you using?
Have you recently updated the version?
What version and build of YF are you using? E.g. 7.1, Sept?
Have you attempted to increase the JVM Max Memory settings? I have linked in the relevant Forum post that discusses this.
I've also linked in THIS info from stackoverflow that may be of assistance.
Please let us know and we will continue to look at this for you.
Yes, we've tried increasing heap size. Our current setup looks like this:
JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx8192m"
Application Version: 7.1
Java Version: 1.7.0_80
Thank you for your assistance.
Thank you for getting back to us and for providing some additional information.
We are wondering if you can try updating your version of Java? Either just going to the
next version from what you are currently using or upgrading to the latest release.
Is it also possible to recreate this crash and then send us the full YF log files, noting
the time that the crash occurred? There may be some additional information in the logs
that could prove beneficial. We would also request that you send the logs to our support
email address and reference the topic of this forum post.
Let me know what you think.
We tried the most recent java version (Java SE 8 Update 60) and the java version mentioned in the stackoverflow link (Java 1.7.0_25) but the issue occurred both ways.
We can recreate the issue and sent you the log files. Could you please let us know which particular logs should we send to you? We are tracking the issue through the catalina.out log.
Thank you for all your suggestions,
If you are able to replicate the crash and then capture the yellowfin.log and catalina.out log that should hopefully be what
we are looking for.