Bug 220523 – evolution-mail crashes when evolution is started

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 220523 - evolution-mail crashes when evolution is started


Summary:	evolution-mail crashes when evolution is started


Status:	RESOLVED DUPLICATE of bug 216733

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	unspecified
Hardware:	Other All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-02-14 17:50 UTC by kreucher
Modified:	2002-04-30 22:07 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description kreucher 2002-02-14 17:50:11 UTC

Package: Evolution
Priority: Normal
Version: 1.0.2
Synopsis: evolution-mail crashes when evolution is started
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
i was playing around with the "online/offline" button in the mail and
then all the sudden evolution-mail crashed. i closed evolution and now
when i start it back up evolution-mail crashes. tryed killev... no
help.

oh btw, as a seperate issue, evolution-summary pegs my cpu ALOT.



Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 (LWP 896)]
[New Thread 2049 (LWP 904)]
[New Thread 1026 (LWP 905)]
[New Thread 2051 (LWP 906)]
[New Thread 3076 (LWP 907)]
[New Thread 4101 (LWP 968)]
[New Thread 5126 (LWP 969)]

0x410a3ca9 in __wait4 () from /lib/i686/libc.so.6

+ Trace 17771

Thread 7 (Thread 5126 (LWP 969))

#0 __sigsuspend
at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
#1 __pthread_wait_for_restart_signal
at pthread.c line 969
#2 __pthread_alt_lock
at restart.h line 34
#3 __pthread_mutex_lock
at mutex.c line 120
#4 message_browser_get_type
#5 pthread_sighandler
at signals.c line 97
#6 <signal handler called>
#7 word_index_mem_dump_info
#8 ibex_create_word_index_mem
#9 ibex_unindex
#10 camel_folder_summary_info_new_from_parser
at camel-folder-summary.c line 875
#11 camel_folder_summary_add_from_parser
at camel-folder-summary.c line 787
#12 summary_rebuild
at camel-mbox-summary.c line 293
#13 summary_update
at camel-mbox-summary.c line 342
#14 mbox_summary_check
at camel-mbox-summary.c line 389
#15 camel_local_summary_check
at camel-local-summary.c line 256
#16 camel_local_folder_construct
at camel-local-folder.c line 241
#17 camel_mbox_folder_new
at camel-mbox-folder.c line 131
#18 get_folder
at camel-mbox-store.c line 125
#19 camel_store_get_folder
at camel-store.c line 253
#20 mail_importer_uninit
#21 mail_importer_uninit
#22 camel_store_get_folder
at camel-store.c line 253
#23 mail_tool_uri_to_folder
#24 mail_build_attachment
#25 mail_msg_wait_all
#26 thread_received_msg
at e-msgport.c line 469
#27 thread_dispatch
at e-msgport.c line 550
#28 pthread_start_thread
at manager.c line 284



Unknown reporter: kreucher@msu.edu, changed to bugbuddy-import@ximian.com.

Comment 1 Gerardo Marin 2002-03-30 06:32:40 UTC

The only other report with a crash in FakeCString is bug 217842.  It 
also mentions a CPU hog... however traces look quite different. Does 
this make any sense?

Comment 2 Gerardo Marin 2002-04-30 22:07:46 UTC


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