Sorry for the late reply, I've posted a patch to resolve this issue.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51205
On 16 May 2011 10:20, Jeremias Maerki wrote:
> Hi Mehdi
>
> Looks like a typo to me. See:
> http://www4.infoprintsolutionscompany.com/help/topic/com.ibm.printers.afpprodu
Hi Tarun,
First, this question would be (and actually has been) better asked on fop-users.
Second, the error message is usually correct. Somewhere in your fo file you
have a table which has more cells in one row than table-columns defined. FOP
0.20 ignored such cells, FOP 1.0 complains.
Mit fre
https://issues.apache.org/bugzilla/show_bug.cgi?id=51150
--- Comment #2 from Unlogic 2011-05-18 12:12:27 UTC ---
I've done some more research and from what I can see DecimalFormatCache is the
only place in the FOP source where ThreadLocal is used. So there doesn't seem
to be any more memory leaks
I am using Fop 1.0.
I tried using Fop to transform a single document. When I got a little
over 100 pages my FO file was over 5 MB. The transform crashed with a
Java heap out of memory error.
I managed to break the input down, as I'm using embedded code generating
the input programmatically, and t
Just a wild thought. But is there a way you could possibly get the JVM to
garbage collect between each run? Maybe that might free the memory up?
Thanks.
-Mike
On 18/05/11 13:20, Eric Douglas wrote:
I am using Fop 1.0.
I tried using Fop to transform a single document. When I got a little over
https://issues.apache.org/bugzilla/show_bug.cgi?id=51218
Bug #: 51218
Summary: FOP is unable to create PDF if there is an unusually
large paragraph.
Product: Fop
Version: 0.20.1
Platform: PC
OS/Version: All
https://issues.apache.org/bugzilla/show_bug.cgi?id=51218
--- Comment #1 from Mehdi Houshmand 2011-05-18 13:02:45 UTC
---
Have you tried using FOP 1.0? 0.20 is no longer supported.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this ma
https://issues.apache.org/bugzilla/show_bug.cgi?id=51218
Abhijeet changed:
What|Removed |Added
Version|0.20.1 |1.0
--
Configure bugmail: https://issu
https://issues.apache.org/bugzilla/show_bug.cgi?id=51218
--- Comment #2 from Abhijeet 2011-05-18 13:06:27 UTC
---
Corrected the version. It is 1.0.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the
I don't know when it does it's automatic garbage collection if that's
the only issue.
I tried adding the statement to tell it to garbage collect right after
calling the method to render to PNG, though I believe I heard that
doesn't actually do garbage collection right when that executes. It
didn't
When I tested over 130 pages the PNG render crashed with this dump.
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at
java.lang.AbstractStringBuilder.(AbstractStringBuilder.java:45)
at java.lang.StringBuilder.(StringBuilder.java:92)
at org.apache.fop.area.inline.SpaceAr
Hi Eric,
I'd run a debugger (available with modern JDKs). Set a breakpoint after the
first run and memory profiling should tell you, which objects are still in
memory and why.
Regards,
Georg Datterl
-- Kontakt --
Georg Datterl
Geneon media solutions gmbh
Gutenstetter Straße 8a
90449
If there's no obvious answer as to what Fop might be doing wrong or what I
might be doing wrong that would be my next guess, except I've never done that
so I'd have to figure out how.
From: Georg Datterl [mailto:georg.datt...@geneon.de]
Sent: Wednesday, May 18,
Hi Eric,
On a windows system it's quite straight-forward. Run your application in your
IDE. Stop at breakpoint. Run VisualVM. You will get a list of running java
processes, including your application. A few clicks will get you a memory
profile and there you can see a tree structure, where each
Hi Eric,
Fop calculates layout in page sequence chunks, so try breaking up your pages
into chunks of page sequences. Pages should be available for garbage
collection once the page sequence has been rendered.
Cheers, Adrian.
On May 18, 2011, at 7:24 AM, Michael Rubin wrote:
> Just a wild tho
Hi Eric,
Does your document contain many large SVG's? If so take a look at Bugzilla
#46360. This issue was resolved in rev 997602 of FOP trunk.
Pete
On Wed, May 18, 2011 at 5:10 PM, Adrian Cumiskey
wrote:
> Hi Eric,
>
> Fop calculates layout in page sequence chunks, so try breaking up you
This test run isn't using SVG at all. The PDFRenderer is working, the
PNGRenderer runs out of memory, so it is using images but as output.
I already broke up the input to multiple FOs with multiple calls to the
transform to generate a large document by combining small documents
using the initial-p
https://issues.apache.org/bugzilla/show_bug.cgi?id=51150
--- Comment #3 from Andreas L. Delmelle 2011-05-18
18:28:19 UTC ---
(In reply to comment #2)
> I've done some more research and from what I can see DecimalFormatCache is the
> only place in the FOP source where ThreadLocal is used. So ther
What I could find on int[] references seems to be...
org.apache.fop.render.pdf.PDFRenderer extends
AbstractPathOrientedRenderer implements PDFConfigurationConstants
org.apache.fop.render.bitmap.PNGRenderer extends Java2DRenderer
org.apache.fop.render.java2d.Java2DRenderer extends
AbstractPa
https://issues.apache.org/bugzilla/show_bug.cgi?id=51218
--- Comment #3 from Andreas L. Delmelle 2011-05-18
18:45:18 UTC ---
(In reply to comment #0)
>
> 1. FOP Performs unusually SLOW if there is a large paragraph
> We have noticed that when there is an unusually large paragraph than FOP
> per
On 17 May 2011, at 00:58, Giuseppe Briotti wrote:
Hi Guiseppe
>
> TKS Andreas, in the meanwhile I setup Eclipse and FOP packages in a project,
> and started to take a look at the code and structure.
>
> I didn't find a class diagram or some overview documentation (just a
> "bigpicture" page
Thanks Andreas.
I'll "travel" the code a bit and then come back. If I'll success in such
coding, I'll write all on the wiki ("how I did it!")
G.
--
Giuseppe Briotti
g.brio...@gmail.com
"Alme Sol, curru nitido diem qui
promis et celas aliusque et idem
nasceris, possis nihil urbe Roma
visere m
Hi Eric,
That sounds interesting. If you run the transformer for each page and set a
breakpoint after the first run, there (IMHO) should not be a reference to any
fop object. Ignore the int[]s first, they are used everywhere. Concentrate on
the fop objects which should not be there. You could a
23 matches
Mail list logo