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 412351 - crash in Image Viewer: Going through a few high...
crash in Image Viewer: Going through a few high...
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-02-26 18:54 UTC by Tom Harris
Modified: 2007-02-26 20:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Tom Harris 2007-02-26 18:54:01 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Going through a few high-ish res photos (2.5Mb each).


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

Memory status: size: 196534272 vsize: 0 resident: 196534272 share: 0 rss: 139243520 rss_rlim: 0
CPU usage: start_time: 1172515930 rtime: 0 utime: 1275 stime: 0 cutime:1228 cstime: 0 timeout: 47 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 -1225996096 (LWP 12224)]
[New Thread -1298682976 (LWP 12228)]
[New Thread -1227969632 (LWP 12225)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 114105

Thread 1 (Thread -1225996096 (LWP 12224))

  • #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-02-26 20:22:14 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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