Memory problem using ICM TGenericDocViewer?

Hello,<br />
<br />
while loading some multi-page documents (with embedded colored pictures) into
the viewer, we have the problem of <i>out of memory exceptions</i>,
thrown by the JVM.<br />
<br />
Our JVM is configured like this:<br />
Xms:128MB / Xmx:512MB<br />
<br />
We have just two (!) MO:DCA documents:<br />
<br />
The first document has 16 pages (6 colored and 10 black/white images) in 1.2MB
disk space.<br />
The second has 20 pages (8 colored and 12 black/white images) in 1.4MB disk
space.<br />
<br />
When loading those two documentes into the TGenericDocViewer (configured as a
standalone Java application) we recognized that the application consumes a huge
amount of memory space as follows:<br />
<br />
Without any document (after start): 140.8MB<br />
After loading first document: 251.3MB<br />
After loading second document: 515.5MB<br />
<br />
As comparison:<br />
<br />
When loading these two documents with ImagePlus IWPM, it just needs 1/20 of the
memory (approx. 21MB)!<br />
<br />
My questions are:<br />
<br />
a) Why does the TGenericDocViewer take such a large amount of memory?<br
/>
b) When I close all documents and open another one, the viewer asks for more
memory - why? No memory is deallocated by the viewer after closing the document
tabs. Just when starting the garbage collector using the java console it holds
all the memory.<br />
c) Are there some workarounds or quick solutions? <br />
<br />

Hi there,<br />
<br />
is there already a solution for this?<br />
<br />
We got exactly the same behavior while loading color MO:DCA docs / images<br
/>
into the viewer. A tiny document with a couple of pages ( approx. 1 MB on file
system) takes up<br />
a huge amount of memory (approx. 200-250 Megs) in the RAM while the document is
rendered and the thumbnails<br />
are being created.<br />
<br />
However we didn't experience the problem when <br />
loading a single image (TIFF, GIF, JPG) into the viwer.<br />
The memory consumption was just a little more than the viewer<br />
application takes in idle state.<br />
<br />
So in my oppinion it would assume that it has something to do with the<br
/>
MO:DCA wrapper plus the additional MO:DCA image properties / meta
information<br />
saved together with the documents / images, because the difference <br />
of memory consumption between the pure image data loaded up into the viewer
<br />
and the full MO:DCA information has about a ratio of 1:20.<br />
<br />
Since this problem still exists, we probably won't be using this viewer,<br
/>
because this would be uneconomic in terms of memory usage of the client
pcs.<br />
<br />
Hope someone posts a solution for this problem.<br />
<br />
Thanks in advance,<br />
<br />
Eric Bredtmann<br />
<ul class="jive-dash">
<li>TIMETOACT Software Group -</li>
</ul>