SVG Preview grinds computer to halt

[mrbeardy]

I created a very small and simple SVG using Open Office Draw (see attachment). When Image Viewer tries to open it it quickly claims the remaining 1 gig of RAM and the system load quickly reaches 100% grinding everything to a halt (alt-ctrl-backspace time).

Just did an experiment and when previewing it is the process with the command 'eog' that is taking all the memory. Kill the process and everything returns to normal.

[Tim McNamara (tim-clicks)]

Hi,

I've selected the correct package for this bug. An expert will get in touch as soon as possible.

Could you please provide some more information:

Which version of Ubuntu and the Image Viewer are you running (Click Help > About in an image that opens correctly) are you running?

Have you tried opening SVG files in other applications, for example in a web browser or Inkscape? That might help identify whether the cause is related to the Image Viewer or the OOo.org.

[mrbeardy (mrbeardy)]

Thanks for the advice on improving the bug report Tim.

Ubuntu Version: 8.04
Image Viewer Version: Eye of GNOME 2.22.3

Interestingly it will open in Inkscape 0.46 fine and allows one to see that it is a very simple SVG file with only a few objects. However it causes the 100% load problem in the following viewers:

- Eye of GNOME 2.22.3
- Mirage 0.9
- gThumb 2.10.8

These viewers were available in Add/Remove software

When I look at the XML in a text editor in my, non-expert, opinion there is nothing in there complicated to render that would tax a system to 100% (ie complicated gradients and transforms)

Incidentally the file's XML validates using http://www.validome.org/xml/validate/

[Sebastien Bacher (seb128)]

confirmed on jaunty and seems to be a librsvg issue

[Sebastien Bacher (seb128)]

the current jaunty version seems to just refuse to load the image, can you confirm that's the case too on your installation?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.