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 396708 - crash in Image Viewer: Moving forward / backwar...
crash in Image Viewer: Moving forward / backwar...
Status: RESOLVED DUPLICATE of bug 354106
Product: eog
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-15 00:46 UTC by quasimod
Modified: 2007-01-15 02:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description quasimod 2007-01-15 00:46:21 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Moving forward / backward (could be faster than full loading of the image) at full screen


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 125435904 vsize: 0 resident: 125435904 share: 0 rss: 87949312 rss_rlim: 0
CPU usage: start_time: 1168821908 rtime: 0 utime: 751 stime: 0 cutime:713 cstime: 0 timeout: 38 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226398032 (LWP 22614)]
[New Thread -1272042592 (LWP 22618)]
[New Thread -1228092512 (LWP 22615)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 102254

Thread 1 (Thread -1226398032 (LWP 22614))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 cmsCloseProfile
    from /usr/lib/liblcms.so.1
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 eog_image_free_mem_private
  • #0 __kernel_vsyscall 






Comment 1


Claudio Saavedra





          2007-01-15 02:39:21 UTC
        



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