large jpeg file crashes Eye of Gnome

Bug #1573447 reported by Ophir LOJKINE
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
eog (Ubuntu)
Confirmed
High
Unassigned

Bug Description

This large jpeg image (https://www.dropbox.com/s/0277bt6uy33v495/babel17.jpg?dl=0) crashes Eye of Gnome.
It can be opened without problems in gimp.
Before crashing, eog reports:
    (eog:24304): Gdk-WARNING **: eog: Fatal IO error 2 (Aucun fichier ou dossier de ce type) on X server :0.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

What version of Ubuntu and video card/driver are you using?

Changed in eog (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Jose Gómez (adler-dreamcoder) wrote :

This is happening for me as well. I am using Ubuntu 16.04, GNOME 3.20, nVidia GT750M with proprietary driver.

Revision history for this message
Jose Gómez (adler-dreamcoder) wrote :

Note, though that in my case I don't see any error if I launch it in a terminal. The system halts for a few seconds while loading the file, and then eog just crashes. It doesn't give me the chance to send an error report.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for eog (Ubuntu) because there has been no activity for 60 days.]

Changed in eog (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Ville Ranki (ville-ranki) wrote :

Still happening under Ubuntu 18.04.

I have a large (88mb) jpeg with this info:
JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, baseline, precision 8, 22678x14939, frames 3

eog crashes every time when trying to open it, with following stack trace:

#0 __memset_avx2_erms () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:141
#1 0x00007ffff5b970d1 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#2 0x00007ffff5b63e83 in cairo_surface_create_similar_image () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#3 0x00007ffff5b64070 in cairo_surface_create_similar () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
#4 0x00007ffff5e5f0b0 in gdk_window_create_similar_surface () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#5 0x00007ffff7b980ec in ?? () from /usr/lib/x86_64-linux-gnu/eog/libeog.so
#6 0x00007ffff7b9a803 in eog_scroll_view_set_image () from /usr/lib/x86_64-linux-gnu/eog/libeog.so
#7 0x00007ffff7bac678 in ?? () from /usr/lib/x86_64-linux-gnu/eog/libeog.so
#8 0x00007ffff7bad026 in ?? () from /usr/lib/x86_64-linux-gnu/eog/libeog.so
#9 0x00007ffff7919f6d in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007ffff792cd3e in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007ffff79353f5 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007ffff7935e0f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007ffff7b86869 in ?? () from /usr/lib/x86_64-linux-gnu/eog/libeog.so
#14 0x00007ffff76400f5 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff76404c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff764054c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff72f8d2d in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#18 0x00005555555552b2 in main ()

Might be a bug in cairo instead of eog.

Changed in eog (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Alan Baghumian (alanbach) wrote :

Just tested the above image with eog 3.36.3-0ubuntu1 (Focal) and it crashed (Virtual Machine with 2 CPU cores and 4GB RAM). Tested with eog 42.0-1 (Jammy) and it worked.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.