Extremely poor performance on save when output includes large CDATA nodes (e.g. <i:pgf> nodes from Illustrator)
Bug #1793877 reported by
Marcel Partap
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Inkscape |
Fix Released
|
Medium
|
Patrick Storz | ||
Bug Description
Inkscape 0.92.3 (2405546, 2018-03-11)
What happens when saving an Illustrator SVG is that inkscape writes the SVG up to the <i:pgf id="adobe_
Instead, inkscape should ask to discard the node. And/or write it faster... And remove it with function "Clean up document" ...
Manual fix for me was to kill that node in the XML editor.. c.f. https:/
Revision history for this message
| Marcel Partap (empee584) wrote | #1 |
Revision history for this message
| Patrick Storz (ede123) wrote | #2 |
| summary: |
- adobe_illustrator_pgf tag should be removed on save + Extremely poor performance on save when output includes large CDATA + nodes (e.g. <i:pgf> nodes from Illustrator) |
| tags: | added: performance saving |
| Changed in inkscape: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Patrick Storz (ede123) wrote | #3 |
| Changed in inkscape: | |
| milestone: | none → 0.92.4 |
| status: | Confirmed → In Progress |
| assignee: | nobody → Patrick Storz (ede123) |
Revision history for this message
| Patrick Storz (ede123) wrote | #4 |
Revision history for this message
| Patrick Storz (ede123) wrote | #5 |
| Changed in inkscape: | |
| status: | In Progress → Fix Committed |
| Changed in inkscape: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Performance issue confirmed. After a few minutes I killed Inkscape which only had ~10% of that file saved. This can't be correct.
In principle exporting as "Optimized SVG" would remove that node, too (when disabling "Export editor data"), however that operation includes Inkscape writing the file to disk first, which is as slow as saving the file manually. Scour itself (the Python extension handling optimized SVG output) handles the file without problems.
"Clean up document" is not meant to remove (potentially important) data like this, so let's look at the performance issue first, which should resolve this bug.