Comment 6 for bug 717906

While the file opens reasonable fast in Inkscape, it seems hugely bloated in file size (50 MB vector data compared to what is visible on canvas). Trying the first obvious step to do house-keeping (File > Vacuum Defs) brought down my system to nearly a stand-still and I had to interrupt it (tested with Inkscape 0.48+devel r10049 on OS X 10.5.8 i386, 2GM RAM).

Even regularly closing the Inkscape window without any edits, cause memory usage of inkscape to explode and grab what it can get from the system (I had to killed the process twice).

Maybe you could explain how you got an SVG file in such a state? From what I can gather by grepping some keywords, the file seems to have been edited in Adobe Illustrator as well as in Corel Draw (which must have imported tons of unneeded stuff from Inkscape SVG files as well as have left their proprietary footmarks all over the file).

Some data (line counts from grep output) for internal bug triage:

Adobe Illustrator and CoralDraw:
  Illustrator foreignObjects: 390 (grep for 'i:pgf')
  CorelDraw Layers: 102

More troubling in my mind:
  sodipodi:namedview: 14501 (a regular Inkscape SVG file has only 1)

Do you work with all those layers? Most of them seem empty…
  Inkscape layers: 1838 (grep for 'inkscape:groupmode="layer"')

You also seem to have used custom swatches intensely: there are 475 colors (one-stop gradients) defined in the Auto-palette for the document.
  Colors in Auto-palette: 475 (grep for 'osb:paint')

At the moment I don't know how a) Inkscape is supposed to handle such a file and b) if so, how to best "get rid" of the unneeded stuff (14500 'namedview' definitions, nearly 2000 groupmode 'layer' attributes, which apparently boil down to 28 unique labels, etc.).

These numbers should be ok:
  Images: 0
  Paths: 5393