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 536633 - crash in Image Viewer: Found a BUG in EOV. It's...
crash in Image Viewer: Found a BUG in EOV. It's...
Status: RESOLVED DUPLICATE of bug 505085
Product: eog
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
: 536631 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-06-04 16:00 UTC by marco.balduzzi
Modified: 2008-06-05 12:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description marco.balduzzi 2008-06-04 16:00:55 UTC
Version: 2.22.0

What were you doing when the application crashed?
Found a BUG in EOV. It's REPRODUCEBLE each time I open the image. 
It could be an overflow. The image is 1.3MB Large (3948*4845 pixels). The image is opened correctly by Firefox.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 76500992 vsize: 76500992 resident: 21037056 share: 12902400 rss: 21037056 rss_rlim: 4294967295
CPU usage: start_time: 1212595086 rtime: 133 utime: 123 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/eog'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bc8720 (LWP 28472)]
[New Thread 0xb6a15b90 (LWP 28473)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread 0xb6a15b90 (LWP 28473))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #10 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??


----------- .xsession-errors (12000 sec old) ---------------------
[00000338] access_mms access warning: detected packet lost (6627705 != 6627704)
[00000338] access_mms access warning: detected packet lost (6627707 != 6627706)
[00000338] access_mms access warning: detected packet lost (6627709 != 6627708)
[00000338] access_mms access warning: detected packet lost (6627711 != 6627710)
[00000338] access_mms access warning: detected packet lost (6627713 != 6627712)
[00000338] access_mms access warning: detected packet lost (6627715 != 6627714)
[00000338] access_mms access warning: detected packet lost (6627717 != 6627716)
[00000338] access_mms access warning: detected packet lost (6627720 != 6627719)
[00000338] access_mms access warning: detected packet lost (6627722 != 6627721)
[00000338] access_mms access warning: detected packet lost (6627724 != 6627723)
[00000338] access_mms access warning: detected packet lost (6627726 != 6627725)
[00000338] access_mms access warning: detected packet lost (6627728 != 6627727)
[00000338] access_mms access warning: detected packet lost (6627730 != 6627729)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Felix Riemann 2008-06-04 16:28:17 UTC
Could you please attach the image here if possible? 3948*4845 px shouldn't be a problem for eog.
Comment 2 Felix Riemann 2008-06-05 12:33:52 UTC
*** Bug 536631 has been marked as a duplicate of this bug. ***
Comment 3 Felix Riemann 2008-06-05 12:36:24 UTC
I was in contact with Marco by mail and we could confirm that this is actually bug  505085.
---------------------------------------------------------------------------------
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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