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 217842 - Crash: Evolution freezes and puts CPU at 100% when loading
Crash: Evolution freezes and puts CPU at 100% when loading
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal blocker
: ---
Assigned To: Not Zed
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-12-23 16:52 UTC by Quentin Smith
Modified: 2002-04-23 23:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Quentin Smith 2001-12-23 16:57:05 UTC
Package: Evolution
Priority: Blocker
Version: 1.0
Synopsis: Evolution freezes and puts CPU at 100% when loading
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Have a full mailbox (thousands of messages) and launch evolution.
Depending on the messages, you may or may not get the problem. I believe
it is related to bad mime messages. The CPU goes up to 100% and stays
there until the evolution-mail process is killed.



Debugging Information:

(no debugging symbols found)...0x80bb044 in fakeCString ()

Thread 3 (Thread 1318 (initial thread))

  • #0 __poll
    at ../sysdeps/unix/sysv/linux/poll.c line 45
  • #1 g_main_poll
    at gmain.c line 1034
  • #2 g_main_iterate
    at gmain.c line 808
  • #3 g_main_iteration
    at gmain.c line 884
  • #4 gtk_main_iteration
    at gtkmain.c line 220
  • #5 mail_msg_wait
  • #6 GNOME_Evolution_MailFilter_removeFilter
  • #7 gtk_marshal_NONE__POINTER_POINTER
    at gtkmarshal.c line 171
  • #8 gtk_handlers_run
    at gtksignal.c line 1917
  • #9 gtk_signal_real_emit
    at gtksignal.c line 1477
  • #10 gtk_signal_emit
    at gtksignal.c line 234
  • #11 impl_setOwner
    at evolution-shell-component.c line 400
  • #12 _ORBIT_skel_GNOME_Evolution_ShellComponent_setOwner
    at Evolution-skels.c line 901
  • #13 ORBit_POA_handle_request
    at orbit_poa.c line 349
  • #14 ORBit_handle_incoming_request
    at server.c line 90
  • #15 ORBit_handle_incoming_message
    at server.c line 160
  • #16 giop_main_handle_connection
    at connection.c line 1135
  • #17 orb_handle_connection
    at oaf-mainloop.c line 70
  • #18 g_io_unix_dispatch
    at giounix.c line 135
  • #19 g_main_dispatch
    at gmain.c line 656
  • #20 g_main_iterate
    at gmain.c line 877
  • #21 g_main_run
    at gmain.c line 884
  • #22 gtk_main
    at gtkmain.c line 220
  • #23 bonobo_main
    at bonobo-main.c line 95
  • #24 main
  • #25 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 90

Comment 1 Not Zed 2002-01-31 03:46:34 UTC
Does it lock forever, like more than 10 minutes? (i assume you dont
have 10k messages).

Does it ever leave that function 'complete' above.
(in gdb try:
  frame 2
  fin
)

If not, can you try and idenfity the specific message that is causing
the problem and attach it here?
Comment 2 Jeffrey Stedfast 2002-04-23 23:59:55 UTC
Presumed fixed based on lack of user response.