RE: How FOP renderred my 17,344 page document...

2001-07-31 Thread COFFMAN Steven
nt: Friday, July 20, 2001 12:33 AM To: [EMAIL PROTECTED] Subject: Re: How FOP renderred my 17,344 page document... AAh, I have a working multi -threaded memory patch that i developed and its been lying around with me simply because i just dont want to figure how to commit from my stupid windoze m

Re: How FOP renderred my 17,344 page document...

2001-07-18 Thread Seshadri G.K.
- Original Message - From: Mark <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, July 16, 2001 8:56 AM Subject: Re: How FOP renderred my 17,344 page document... > Hi Fopsters > > > I'm personally only offended by bein

Re: How FOP renderred my 17,344 page document...

2001-07-18 Thread Mark
Hi Fopsters> I'm personally only offended by being referred to as a "fopsicle". Just > kidding. :-)I just love the word 'fop', it has so many literary possibilities. :-)> Seriously, this is great stuff. You should be aware that the initial memory > buffering that you see with the -buf switch i

Re: How FOP renderred my 17,344 page document...

2001-07-15 Thread Arved Sandstrom
At 05:41 PM 7/15/01 +1000, Mark wrote: > I hope noone is offended by my work/writing on this stuff, I realise that >FOP is experimental but the number of changes are surprisingly small and >the results are just so cool. Memory use is significantly reduced for all >cases where there is more than on

How FOP renderred my 17,344 page document...

2001-07-15 Thread Mark
Hey there fopsicles Well I just generated a 17,344 page document using FOP on Linux JDK1.3.1 with a 64Mb heap into PDF. I also tried processing a 34,688 page document but ran out of memory on page 33,287 (bummer!). I suspect that the OOM error is almost certainly due to the PDFRenderer keeping