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 622527 - eog does not display huge images (and crashes)
eog does not display huge images (and crashes)
Status: RESOLVED DUPLICATE of bug 163090
Product: eog
Classification: Core
Component: image viewer
2.30.x
Other Linux
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-23 20:53 UTC by Luke Hutchison
Modified: 2010-07-05 20:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
a test SVG file, export this as a 52000 pix wide PNG in Inkscape. (230.95 KB, application/x-gzip)
2010-06-23 21:28 UTC, Luke Hutchison 		Details

Description Luke Hutchison 2010-06-23 20:53:17 UTC 
I was trying to view an image that was approximately 52000x1200 pixels, and EOG has a number of problems with this:

-- EOG initially shows the whole image scaled down to fit in the window, and it is correctly thumbnailed from the left hand side to about 2/3rds of the way across the image (I assume this is pixel column 32,768), from which point to the right hand side all that shows is the checkerboard background.

-- When zooming in, the image initially is filled with uninitialized data -- mostly-black pixels with random-colored pixels mixed in -- and then those tiles are overwritten by the scaled image.

-- If I view the image at 100% then the image is corrupted (it displays single pixel columns from the image repeated in bands 50-100 pixels wide).  Moving to any zoom other than 100% correctly displays the first two-thirds of the image (see above).

GIMP loads and displays the image fine.
Comment 1 Luke Hutchison 2010-06-23 20:55:32 UTC 
Also I scaled to 100% and then scrolled around, and got a segfault.  I have not been able to duplicate though.
Comment 2 Fabio Durán Verdugo 2010-06-23 21:21:17 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 3 Luke Hutchison 2010-06-23 21:27:31 UTC 
The non-crashing part of this bug is very easy to duplicate, just create a wide image in Inkscape and save it as a PNG file.  I'll attach an SVG file you can use for this, just export it as a 52,000 pixel wide PNG and try viewing it.  I'll work on duplicating the crash and if I manage it I'll attach a backtrace here.  However there were several non-crash aspects to this bug that should also be addressed.
Comment 4 Luke Hutchison 2010-06-23 21:28:50 UTC 
Created attachment 164439 [details]
a test SVG file, export this as a 52000 pix wide PNG in Inkscape.

(I'm not attaching the PNG file this generates, because it is too big)
Comment 5 Felix Riemann 2010-07-05 20:15:15 UTC 
eog's 32k pixels limitations is actually a gdk-pixbuf one. Check bug 163090.

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 163090 ***