After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656798 - Opening svg 1.1 file via Eye of GNOME consumes tremendous resources
Opening svg 1.1 file via Eye of GNOME consumes tremendous resources
Status: RESOLVED DUPLICATE of bug 340963
Product: eog
Classification: Core
Component: general
2.32.x
Other Linux
: Normal major
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-08-18 03:37 UTC by Christopher M. Penalver
Modified: 2012-01-18 11:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christopher M. Penalver 2011-08-18 03:37:40 UTC
1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

2) apt-cache policy eog
eog:
  Installed: 2.32.1-0ubuntu2
  Candidate: 2.32.1-0ubuntu2
  Version table:
 *** 2.32.1-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen in Eye of GNOME via the Terminal:

cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/384566/+attachment/602159/+files/CodigoGray4Bits2.svg && eog CodigoGray4Bits2.svg

is it opens quickly and successfully.

4) What happens instead is eog consumes a tremendous amount of system resources, making all other programs very sluggish and unusable until the eog process is terminated. The file passed the W3C Validator ( http://validator.w3.org/ ) as svg 1.1.
Comment 1 Felix Riemann 2012-01-18 11:28:05 UTC
That's a known problem with SVGs exported from OpenOffice/LibreOffice causing eog allocate way to much memory.
There's no really sane fix for that currently. Personally I hope it might go away once eog doesn't need any (fullscale) pixbuf representation of SVGs anymore.
---------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 340963 ***