Bug 529236 – crash in emf_insert_cache at em-format.c:110

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 529236 - crash in emf_insert_cache at em-format.c:110


Summary:	crash in emf_insert_cache at em-format.c:110


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.12.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-21 16:14 UTC by wduckworth
Modified:	2008-07-18 07:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description wduckworth 2008-04-21 16:14:31 UTC

Version: 2.12

What were you doing when the application crashed?



Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.24.3-50.fc8PAE #1 SMP Thu Mar 20 14:14:35 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 241397760 vsize: 241397760 resident: 90722304 share: 24948736 rss: 90718208 rss_rlim: 4294967295
CPU usage: start_time: 1208790539 rtime: 4279 utime: 3998 stime: 281 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209071856 (LWP 18275)]
[New Thread -1302615152 (LWP 25689)]
[New Thread -1243128944 (LWP 25687)]
[New Thread -1289749616 (LWP 18291)]
[New Thread -1276761200 (LWP 18287)]
[New Thread -1265636464 (LWP 18284)]
[New Thread -1255146608 (LWP 18281)]
[New Thread -1232634992 (LWP 18278)]
0x00110410 in __kernel_vsyscall ()

+ Trace 195788

Thread 1 (Thread -1209071856 (LWP 18275))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 strlen
from /lib/libc.so.6
#10 emf_insert_cache
at em-format.c line 110
#11 em_format_set_inline
at em-format.c line 1022
#12 efhd_attachment_show
at em-format-html-display.c line 1429
#13 efhd_attachment_button_show
at em-format-html-display.c line 1435
#14 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
#24 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#0 __kernel_vsyscall

Comment 1 Tobias Mueller 2008-04-21 18:51:33 UTC

Hi,

thanks for your bugreport with that neat stacktrace.
Looks like bug 467763 or bug 410733 to me which should have been fixed.

Comment 2 Akhil Laddha 2008-06-13 05:09:01 UTC

can you please check in 2.22.2, i guess fixed by bug 511337, thanks.

Comment 3 Akhil Laddha 2008-07-18 07:03:34 UTC

Please feel free to reopen this bug if the problem still occurs with a newer
version of GNOME 2.22.3.