Hi,
We are using Aspose.Cells and Aspose.PDF for Java on a Linux environment.
Because it is executed in a headless session, we needed to use the following options in our JVM:
-DAspose.Cells.Disable=SunFontManager
-Djava.awt.headless=true
Without these options, we have experienced some JVM crashes during Aspose usage.
Now we are experiencing some intensive memory usage in our application, and we are wondering if it is linked to the use of these options. Have you ever benchmarked the memory footprint of these options? If yes, can you please let us know? If not, any chance you could have a look?
Thanks in advance and regards.
<!–[if gte mso 9]>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:DontVertAlignCellWithSp/>
<w:DontBreakConstrainedForcedTables/>
<w:DontVertAlignInTxbx/>
<w:Word11KerningPairs/>
<w:CachedColBalance/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=“Cambria Math”/>
<m:brkBin m:val=“before”/>
<m:brkBinSub m:val="–"/>
<m:smallFrac m:val=“off”/>
<m:dispDef/>
<m:lMargin m:val=“0”/>
<m:rMargin m:val=“0”/>
<m:defJc m:val=“centerGroup”/>
<m:wrapIndent m:val=“1440”/>
<m:intLim m:val=“subSup”/>
<m:naryLim m:val=“undOvr”/>
</m:mathPr></w:WordDocument>
<![endif]–>
Hi Vincent,
Thank you for contacting Aspose support.
Unfortunately, we haven’t bench-marked the aforesaid options in perspective of Aspose.Cells for Java APIs, however, we will look into the presented scenario to provide updates in this regard. We need your environment details such as Operating System version/architecture, JDK type/version to simulate it on our side. Moreover, we will need the exact source code lines as well as the template spreadsheet(s) triggering the memory spikes.
Before you provide the above requested information, please make sure you are using the latest version of Aspose.Cells for Java. Reason being, with recent releases we have improved the memory utilization by providing memory configurations that can be used to lower the memory cost. We hope you will be able to overcome the problem using these preferences.
Thank you for your reply.
We haven’t isolated yet the part of the code that provokes Heap Space memory outages. So I’m not even certain it is linked to Aspose. It just happens that we have been working with Aspose Cells, among other features, in the period where memory “leaks” have appeared.
We are still in the process of identifying the root cause and I just wanted to know if you had witnessed such behaviors already. If we can find a scenario that can reproduce the issue, and it seems linked to Aspose Cells, I will of course share it with you.
Regards
Hi Vincent,
Sure, please keep us posted with updates in this regard. In case you need our further assistance, please feel free to contact us any time.