Bug 496482 – crash in Image Viewer:

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 496482 - crash in Image Viewer:


Summary:	crash in Image Viewer:


Status:	RESOLVED DUPLICATE of bug 357405

Product:	eog
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	EOG Maintainers
QA Contact:	EOG Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-13 15:45 UTC by wust0017
Modified:	2007-11-14 19:12 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description wust0017 2007-11-13 15:45:30 UTC

Version: 2.18.0.1

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 921067520 vsize: 921067520 resident: 318312448 share: 5672960 rss: 318312448 rss_rlim: 4294967295
CPU usage: start_time: 1194967224 rtime: 38322 utime: 35783 stime: 2539 cutime:1 cstime: 26 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209121056 (LWP 14720)]
[New Thread -1245135984 (LWP 14764)]
[New Thread -1211511920 (LWP 14722)]
(no debugging symbols found)
0x00c13402 in __kernel_vsyscall ()

+ Trace 177454

Thread 3 (Thread -1211511920 (LWP 14722))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 eog_image_load
#11 ??
#12 eog_job_call_action
#13 ??
#14 g_cclosure_marshal_VOID__VOID
from /lib/libglib-2.0.so.0
#15 start_thread
from /lib/libpthread.so.0
#16 clone
from /lib/libc.so.6



----------- .xsession-errors (318077 sec old) ---------------------
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
[00000394] main private error: subpicture heap is full
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Felix Riemann 2007-11-14 19:12:55 UTC

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 version 2.20. You may want to check for a software upgrade.


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