DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 Alex Giotis alex.gio...@gmail.com changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 Jeremias Maerki jerem...@apache.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #8 from Jeremias Maerki jerem...@apache.org 2010-09-16 02:31:59 EDT --- Patch applied: http://svn.apache.org/viewvc?rev=997599view=rev Thanks, Alexis. One more fix here: http://svn.apache.org/viewvc?rev=997602view=rev That should now be all. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 --- Comment #6 from Alexis Giotis alex.gio...@gmail.com 2010-09-02 05:01:10 EDT --- I can confirm that this issue is valid for FOP 1.0. A workaround is to use a different instance of FopFactory per thread. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 --- Comment #7 from Alexis Giotis alex.gio...@gmail.com 2010-09-02 07:52:22 EDT --- Created an attachment (id=25970) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=25970) Patch to clone the SVG document inside PDFImageHandlerSVG The patch is attached after a short discussion in the fop-dev mailing list. Shortly, in PDFImageHandlerSVG.handleImage() the SVG document is not cloned but in other places it is. Examples of cloning are in ImageConverterSVG2G2D, AbstractGenericSVGHandler, AFPImageHandlerSVG, AFPSVGHandler, Java2DSVGHandler, PSSVGHandler. Before the patch, in a multi-threaded environment parsing of the SVG documents was corrupted with a probability close to 80%. After this, the errors can not be reproduced. This patch contains the smallest change I could do, is for a single file and should be safe to apply. On a side note, normally I would first try to gather the building of the GraphicsNode in a single place and then avoid the document cloning by serializing only the parsing of the SVG. But that would affect more files / projects and would make the processing of the patch more difficult. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 --- Comment #3 from M.H. mhilp...@gmx.de 2008-12-19 02:30:20 PST --- I got a NullPointerException during FOP processing while do transformations were processing concurrently. Both include (the same) SVG image files. - The attribute style represents an invalid CSS declaration (fill:#ef7b00; fill-rule:nonzero; stroke:none; stroke-width:1; stroke-linecap:butt; stroke-linejoin:miter; stroke-dasharray:none;). Original message: java.lang.NullPointerException org.w3c.dom.DOMException: file:/C:/Programme/ddf/xml/images/V10271.svg: The attribute style represents an invalid CSS declaration (fill:#ef7b00; fill-rule:nonzero; stroke:none; stroke-width:1; stroke-linecap:butt; stroke-linejoin:miter; stroke-dasharray:none;). Original message: java.lang.NullPointerException at org.apache.batik.css.engine.CSSEngine.getCascadedStyleMap(Unknown Source) at org.apache.batik.css.engine.CSSEngine.getComputedStyle(Unknown Source) at org.apache.batik.bridge.CSSUtilities.getComputedStyle(Unknown Source) at org.apache.batik.bridge.CSSUtilities.convertDisplay(Unknown Source) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown Source) at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown Source) at org.apache.batik.bridge.GVTBuilder.build(Unknown Source) at org.apache.fop.render.pdf.PDFSVGHandler.renderSVGDocument(PDFSVGHandler.java:188) --- see https://issues.apache.org/bugzilla/show_bug.cgi?id=46418 I guess, there are more threading issues with Batik SVG... -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 --- Comment #4 from Jeremias Maerki jerem...@apache.org 2008-12-19 02:41:23 PST --- A similar bug has been fixed in FOP Trunk as is noted in this bug. Does this error occur with the current FOP Trunk? (In reply to comment #3) I got a NullPointerException during FOP processing while do transformations were processing concurrently. Both include (the same) SVG image files. - The attribute style represents an invalid CSS declaration (fill:#ef7b00; fill-rule:nonzero; stroke:none; stroke-width:1; stroke-linecap:butt; stroke-linejoin:miter; stroke-dasharray:none;). Original message: java.lang.NullPointerException org.w3c.dom.DOMException: file:/C:/Programme/ddf/xml/images/V10271.svg: The attribute style represents an invalid CSS declaration (fill:#ef7b00; fill-rule:nonzero; stroke:none; stroke-width:1; stroke-linecap:butt; stroke-linejoin:miter; stroke-dasharray:none;). Original message: java.lang.NullPointerException at org.apache.batik.css.engine.CSSEngine.getCascadedStyleMap(Unknown Source) at org.apache.batik.css.engine.CSSEngine.getComputedStyle(Unknown Source) at org.apache.batik.bridge.CSSUtilities.getComputedStyle(Unknown Source) at org.apache.batik.bridge.CSSUtilities.convertDisplay(Unknown Source) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown Source) at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown Source) at org.apache.batik.bridge.GVTBuilder.build(Unknown Source) at org.apache.fop.render.pdf.PDFSVGHandler.renderSVGDocument(PDFSVGHandler.java:188) --- see https://issues.apache.org/bugzilla/show_bug.cgi?id=46418 I guess, there are more threading issues with Batik SVG... -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 --- Comment #5 from M.H. mhilp...@gmx.de 2008-12-19 06:37:43 PST --- As this is a multi-threading issue, it's hard to reproduce. I throw lots of jobsat the application but wasn't able to reproduce it for now (with FOP 0.95). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 Jeremias Maerki [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Jeremias Maerki [EMAIL PROTECTED] 2008-12-07 10:04:39 PST --- Issue fixed as discussed on batik-users. http://svn.apache.org/viewvc?rev=724163view=rev http://svn.apache.org/viewvc?rev=724164view=rev I'll keep this open for a bit since I'll have to do the same in the IF branch. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46360] Thread-safety issue rendering SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360 --- Comment #2 from Jeremias Maerki [EMAIL PROTECTED] 2008-12-07 10:07:08 PST --- One more note to self: Need to introduce a flag to indicate whether we're working off a potentially cached SVG DOM or off a DOM that comes from an fo:instream-foreign-object in which the cloning is unnecessary. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
