PiRSquared17 / bout-time

Automatically exported from code.google.com/p/bout-time
1 stars 0 forks source link

Out of Memory Runtime Exception #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
When printing brackets and boutsheets I got a runtime exception indicating 
I was out of memory.  The message was:

java.lang.out of memory Error: Java heap space

This occurred when I was printing bracket and boutsheets.  It happened 
twice.  My recovery was to close BoutTime and reopen which seemed to free 
memory.  The error occurred after I had created and printed several 
Bracket/BoutSheets for multiple mats.  I made sure that the .tmp files 
were closed every time so that only one or two .tmp files were open at a 
time.  My suspicion is that BoutTime is not properly releasing memory.  I 
was running under Vista with 4GB of Ram.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
BoutTime v.05

Please provide any additional information below.

Workaround is to close and re-open the program which seems to clear memory 
pointers. 

Original issue reported on code.google.com by melsw...@austin.rr.com on 18 Jan 2010 at 5:49

Attachments:

GoogleCodeExporter commented 9 years ago
The PDF file generating and viewing is done by icepdf.  We're currently using 
version
3.0.  I found the following on the icepdf.org website regarding 'Memory 
Management
and Caching : 

"As a PDF file is opened and additional pages are viewed, more objects streams 
are
decompressed, and the memory required to display the content grows 
significantly. "

To debug, I attached the netbeans profiler and set it to analyze memory.  I 
launched
BoutTime and opened an existing tournament.  I then generated a BoutSheet 
report that
was large (> 300 pages).  I viewed every page and watched the "Used Memory" 
grow and
grow in the profiler.  I then saw the memory management run and the Used Memory
dropped.  I did this several times but never got the OutOfMemory exception.  

I'll keep trying things along these lines.  

Also to note : there are some tuning properties for icepdf : 

org.icepdf.core.minMemory [string] : Sets the amount of Java heap memory to 
reserve
as a safety buffer to prevent OutOfMemory Exceptions from occurring. If the 
amount of
used Java heap memory is greater than (Max Memory - org.icepdf.core.minMemory), 
the
memory manager will flush pages in the page cache until the required amount of 
Java
heap memory is available.
The default is 5MB.

org.icepdf.core.maxSize [integer] : Specifies the maximum number of pages that 
should
be cached at one time. The default is 0, which results in as many pages as will 
fit
in the available memory being cached. A value of 1 effectively disables the 
page cache.

org.icepdf.core.purgeSize [integer] : Sets the number of pages that are purged 
from
the page cache each time the memory manager attempts to free memory.
Default value is 5 pages.

http://www.icepdf.org/docs/v3_1_0/html/devguide/configuringICEpdf11.html

Original comment by jeff.btpro on 21 Jan 2010 at 7:05

GoogleCodeExporter commented 9 years ago
I believe this was fixed with the update to 3rd party jar files, specifically 
the ICE PDF files.

This needs verification.

Original comment by jeff.btpro on 19 Nov 2011 at 5:04