Bug 441262 – crash in Evolution: Opening a mail message.

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 441262 - crash in Evolution: Opening a mail message.


Summary:	crash in Evolution: Opening a mail message.


Status:	RESOLVED DUPLICATE of bug 467791

Product:	GtkHtml
Classification:	Other
Component:	Rendering
Version:	3.12.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gtkhtml-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-25 19:02 UTC by Jon Schewe
Modified:	2007-08-18 12:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Jon Schewe 2007-05-25 19:02:55 UTC

What were you doing when the application crashed?
Opening a mail message.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 1159176192 vsize: 1159176192 resident: 308682752 share: 24797184 rss: 333479936 rss_rlim: -774895616
CPU usage: start_time: 1179160922 rtime: 138573 utime: 131237 stime: 7336 cutime:309 cstime: 335 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47672731282640 (LWP 7860)]
[New Thread 1107310912 (LWP 11552)]
[New Thread 1174718784 (LWP 7990)]
[New Thread 1157933376 (LWP 7881)]
[New Thread 1157667136 (LWP 7880)]
[New Thread 1149274432 (LWP 7879)]
[New Thread 1140881728 (LWP 7876)]
[New Thread 1132489024 (LWP 7875)]
[New Thread 1124096320 (LWP 7872)]
[New Thread 1115703616 (LWP 7871)]
[New Thread 1098918208 (LWP 7867)]
[New Thread 1090525504 (LWP 7865)]
[New Thread 1082132800 (LWP 7864)]
(no debugging symbols found)
0x00002b5ba9c11c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 136047

Thread 1 (Thread 47672731282640 (LWP 7860))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 html_map_add_shape
from /opt/gnome/lib64/libgtkhtml-3.8.so.15
#4 html_engine_add_object_with_id
from /opt/gnome/lib64/libgtkhtml-3.8.so.15
#5 html_engine_add_object_with_id
from /opt/gnome/lib64/libgtkhtml-3.8.so.15
#6 html_engine_update_focus_if_necessary
from /opt/gnome/lib64/libgtkhtml-3.8.so.15
#7 html_engine_set_editable
from /opt/gnome/lib64/libgtkhtml-3.8.so.15
#8 gtk_html_stream_close
from /opt/gnome/lib64/libgtkhtml-3.8.so.15
#9 em_html_stream_new
from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
#10 em_sync_stream_get_type
from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
#11 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#12 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#13 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#14 bonobo_main
from /opt/gnome/lib64/libbonobo-2.so.0
#15 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Pedro Villavicencio 2007-05-26 01:12:01 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Jon Schewe 2007-05-26 12:30:18 UTC

Unfortunately I've already deleted the message that was causing it.

Comment 3 Pedro Villavicencio 2007-07-16 21:44:33 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 4 André Klapper 2007-08-18 11:39:19 UTC

interesting. this is exactly the same crash that you faced when filing bug 467791.

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

Comment 5 Jon Schewe 2007-08-18 12:47:47 UTC

Except this time I kept the email message :)