This makes batik non-compliant with the SVG specification, additionally I can fairly easily construct just as painful SVG files that bypass this check so I don't think it's very useful. We have in the past taken the position that the issue is that the caller should be time/memory sandboxing the SVG render since valid content can take an arbitrary amount of time/memory.
Thomas On Fri, Jan 7, 2022 at 9:06 AM Simon Steiner (Jira) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/BATIK-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Simon Steiner resolved BATIK-1319. > ---------------------------------- > Fix Version/s: trunk > Resolution: Fixed > > http://svn.apache.org/viewvc?view=revision&revision=1896806 > > > Prevent the use element from being called more than once > > -------------------------------------------------------- > > > > Key: BATIK-1319 > > URL: https://issues.apache.org/jira/browse/BATIK-1319 > > Project: Batik > > Issue Type: Bug > > Reporter: Simon Steiner > > Assignee: Simon Steiner > > Priority: Major > > Fix For: trunk > > > > Attachments: manyuse.svg > > > > > > Converting the attached svg should not result in high memory use > > > > -- > This message was sent by Atlassian Jira > (v8.20.1#820001) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: batik-dev-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: batik-dev-h...@xmlgraphics.apache.org > >
