piovezan Posted October 20, 2009 Share Posted October 20, 2009 Hi,I'm using virtualization (net.sf.jasperreports.engine.fill.JRSwapFileVirtualizer) with some large reports, but my application is still subject to OOEM (java.lang.OutOfMemoryError). After some profiling I have come to the conclusion that most data in the heap is allocated by the swap file handling mechanism (accounting of free blocks and such). This may be related to ( this known bug - obsolete link deleted ), as reports do have subreports, however I also suspect of a poor choice on the virtualization parameters (maxSize for JRSwapFileVirtualizer, and blockSize and minGrowCount for JRSwapFile). I'm specially suspicious of the block size parameter, but haven't been able to find a good formula to calculate it based on the report page contents. Is there such formula, at least for coming up with an approximate value?Thanks,Rodrigo Piovezan Link to comment Share on other sites More sharing options...
lucianc Posted November 30, 2009 Share Posted November 30, 2009 Sounds like you are using a small block size. A typical block size would be in the range of kilos, you can start with something like 4096 for instance.Regards,Lucian Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now