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 223887 - crash while downloading mail
crash while downloading mail
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 229062 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-04-25 19:36 UTC by Clayton
Modified: 2002-08-16 19:33 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Offending message (9.38 KB, text/plain)
2002-04-27 17:22 UTC, Clayton 		Details

Description Clayton 2002-04-25 19:36:19 UTC 
Package: Evolution
Priority: Normal
Version: 1.0.4.99
Synopsis: crash while downloading mail
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Evo bottoms out while I'm trying to download my mail.  It always crashes
on the same message.
If I manually delete this message from my mailserver, it's only a matter
of time  before I receive
another message that produces the same result.



Debugging Information:

[New Thread 1024 (LWP 434)]
[New Thread 2049 (LWP 456)]
[New Thread 1026 (LWP 457)]
[New Thread 2051 (LWP 459)]
[New Thread 3076 (LWP 462)]
[New Thread 5125 (LWP 471)]
0x40f22e29 in __wait4 () from /lib/libc.so.6

+ Trace 21323

Thread 5 (Thread 3076 (LWP 462))

  • #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 segv_redirect
    at main.c line 80
  • #5 pthread_sighandler
    at signals.c line 97
  • #6 <signal handler called>
  • #7 hash_find
    at hash.c line 286
  • #8 unindex_name
    at wordindexmem.c line 302
  • #9 ibex_unindex
    at ibex_block.c line 542
  • #10 camel_folder_summary_info_new_from_message
    at camel-folder-summary.c line 910
  • #11 camel_folder_summary_add_from_message
    at camel-folder-summary.c line 805
  • #12 local_summary_add
    at camel-local-summary.c line 385
  • #13 camel_local_summary_add
    at camel-local-summary.c line 291
  • #14 mbox_append_message
    at camel-mbox-folder.c line 200
  • #15 camel_folder_append_message
    at camel-folder.c line 500
  • #16 mlf_append_message
    at mail-local.c line 288
  • #17 camel_folder_append_message
    at camel-folder.c line 500
  • #18 do_move
    at camel-filter-driver.c line 428
  • #19 e_sexp_term_eval
    at e-sexp.c line 642
  • #20 term_eval_begin
    at e-sexp.c line 586
  • #21 e_sexp_term_eval
    at e-sexp.c line 632
  • #22 e_sexp_eval
    at e-sexp.c line 1214
  • #23 camel_filter_driver_filter_message
    at camel-filter-driver.c line 925
  • #24 camel_filter_driver_filter_folder
    at camel-filter-driver.c line 805
  • #25 filter_folder_filter
    at mail-ops.c line 121
  • #26 fetch_mail_fetch
    at mail-ops.c line 310
  • #27 mail_msg_received
    at mail-mt.c line 500
  • #28 thread_received_msg
    at e-msgport.c line 469
  • #29 thread_dispatch
    at e-msgport.c line 550
  • #30 pthread_start_thread
    at manager.c line 284
Comment 1 Gerardo Marin 2002-04-27 00:15:59 UTC 
Anything usefull within the trace?
Can you attach a copy of the offending message, please?
Comment 2 Clayton 2002-04-27 17:22:30 UTC 
Created attachment 41172 [details]
Offending message
Comment 3 Clayton 2002-04-27 17:23:50 UTC 
If I click on "close" rather than "submit bug report" when evolution
crashes, I don't get a core dump -- so I don't know how to do a trace.

If you can provide me with more specific instructions, I'd be glad to
help out more.
Comment 4 Jeffrey Stedfast 2002-04-27 17:31:06 UTC 
argh, stupid bugzilla.

ok, so I had closed this as fixed because it works fine in cvs HEAD
(aka development branch).
Comment 5 Not Zed 2002-04-30 08:06:25 UTC 
Just some more info (Gerado please note).

Anything crashing in ibex_*() like this involves code that no longer
exists in the 1.1.x development branch _at all_.  As such, we are
closing these bugs as fixed.  We haven't as yet decided to backport
the 1.1.x code to 1.0.x, and as it involves about 3-4 thousand lines
of entirely new code we are unlikely to.

The workaround that usually works in the stable (1.0.x) branch is to
delete the '*.ibex' files in the evolution local tree, stored under
~/evolution/local.  In some cases this isn't sufficient, an offending
mail just has to be moved away from evolution some other way (another
mail client, etc).

Might be nice to close them as duplicates of this or some other bug
(there are a lot of them), incase its such a big problem it needs to
be fixed (but on average it seems that it isn't common enough to
warrant it).

Maybe even a 'known bugs' issue, if we have anywhere to put such things.
Comment 6 Gerardo Marin 2002-08-16 19:33:00 UTC 
*** bug 229062 has been marked as a duplicate of this bug. ***