[Logo] OLD FORUM - Use new one: https://www.CaptainCasa.online/forum
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
PdfRenderer - Out of Memory  XML
Forum Index -> Development
Author Message
brandt

Power User
[Avatar]

Joined: 12/03/2008 16:37:34
Messages: 45
Location: Bern
Offline

Hi Björn,

i try to open a 16 MB PDF document with the PdfRenderer, but i get an OutOfMemoryError.

See attached error-log.

The java applet is started with 256 MB memory. To open such a "small" document should be possible. At least, i hope so

I use the latest version of CaptainCasa (2012-01-23).

Can you reproduce this error?

Regards
Joe
 Filename OutOfMemory.txt [Disk] Download
 Description error-log
 Filesize 26 Kbytes
 Downloaded:  458 time(s)

CaptainCasa

Power User
[Avatar]

Joined: 21/11/2007 12:23:06
Messages: 5555
Offline

Hi,

we just checked...
This internally has to do with the StringBuffer-"Behaviour", we descrbed here: http://www.captaincasademo.com/forum/posts/list/1503.page

For the sending of big strings (upload) we changes things accodingly, for the receiving we did not do so... But will now.

Fix is available on your requets or with regular next update.

Thanks! + Regards,
Björn

Björn Müller, CaptainCasa GmbH
brandt

Power User
[Avatar]

Joined: 12/03/2008 16:37:34
Messages: 45
Location: Bern
Offline

Hi Björn,

thanks a lot.

Next update is perfect.

Regards
Joe

brandt

Power User
[Avatar]

Joined: 12/03/2008 16:37:34
Messages: 45
Location: Bern
Offline

Hi Björn,

after installing the latest version of CaptainCasa i still get an "Out of memory" error when opening a 16 MB PDF-File with the PdfRenderer-Component.

Can you reproduce this error?

Thanks + Regards,
Joe
 Filename OutOfMemory.txt [Disk] Download
 Description
 Filesize 16 Kbytes
 Downloaded:  664 time(s)

CaptainCasa

Power User
[Avatar]

Joined: 21/11/2007 12:23:06
Messages: 5555
Offline

...after phone call + sending some test version:

The problem is now that the OutOfMemory is shifted to the next place where a StringBuffer is used internally - in this case within the SAXParser, which is more and more out of our control, but an "inherent Java feature"...

The current solution unfortunately is only to increase the max-Heapsize accordingly.

Thanks for your support and understanding...

Regards, Björn

Björn Müller, CaptainCasa GmbH
 
Forum Index -> Development
Go to:   
Powered by JForum 2.1.6 © JForum Team