depth of xmlParserMaxDepth insufficient

[amit]

I am trying to import svg file of size 500kb.But inkscape failed to load it.On console it is showing parser error:Excessive depth in document:change xmlParserMaxDepth=1024.Any suggestions how to fix the bug?

[mahfiaz (mahfiaz)]

I compiled the libxml from source setting xmlParserMaxDepth=2048, but this document takes several minutes to load and at least two minutes for every ungroup step. This would take ages.

[mahfiaz (mahfiaz)]

Ishmal found out, that adding (xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink") (without brackets) to the starting svg element would correct the thing.

To remove unnecessary groups the attached php script can be handy.

[bbyak (buliabyak)]

In rev 9775 I added XML_PARSE_HUGE flag to libxml parsing call, so now it no longer errors out on more than 256 nested groups. This bug and my own experience show that such documents happen from time to time, e.g. on import from PDF. The file attached here now opens normally (after fixing its namespace problem) and is editable, even if slow.

[su_v (suv-lp)]

> status: New → Fix Released

It seems that the fix for this report in r9775 was never backported to the stable release branch:
<https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/9775>

trunk, line 305:
<https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/src/xml/repr-io.cpp#L296>

0.48.x, line 297:
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_48_BRANCH/view/head:/src/xml/repr-io.cpp#L288>

Setting bug status to 'Fix Committed' with milestone 0.49.

[Kris (kris-degussem)]

Backport was in revision 9913

[su_v (suv-lp)]

The changes from r9775 (trunk) / r9913 (0.48.x) also help with
- Bug #1073315 “huge text node: out of memory”
  <https://bugs.launchpad.net/inkscape/+bug/1073315>

(parsing error - so far only reported for Fedora - when loading a file with huge embedded bitmap image (> 10MB uuencoded data in single text node)).