Bug 223862 – Evolution-mail crashed

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 223862 - Evolution-mail crashed


Summary:	Evolution-mail crashed


Status:	RESOLVED DUPLICATE of bug 221604

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-04-25 15:06 UTC by jplock
Modified:	2002-05-21 13:36 UTC

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

Description jplock 2002-04-25 15:06:59 UTC

Package: Evolution
Priority: Normal
Version: 1.0.3
Synopsis: Evolution-mail crashed
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
I just closed evolution while it may have still been trying to connect
to my IMAP server and evolution-mail crashed.



Debugging Information:

(no debugging symbols found)...[New Thread 1024 (LWP 19430)]
[New Thread 2049 (LWP 19470)]
[New Thread 7174 (LWP 19479)]
0x40f6b319 in __wait4 () from /lib/libc.so.6

+ Trace 21312

Thread 3 (Thread 7174 (LWP 19479))

#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 __pthread_mutex_lock
at mutex.c line 99
#8 e_msgport_put
at e-msgport.c line 161
#9 mail_async_event_emit
#10 mail_receive_uri
#11 camel_session_register_timeout
at camel-session.c line 676
#12 remote_connect
at camel-remote-store.c line 285
#13 disco_connect
at camel-disco-store.c line 120
#14 camel_service_connect
at camel-service.c line 259
#15 camel_remote_store_connected
at camel-remote-store.c line 569
#16 remote_send_string
at camel-remote-store.c line 337
#17 camel_remote_store_send_string
at camel-remote-store.c line 397
#18 imap_command_start
at camel-imap-command.c line 194
#19 camel_imap_command
at camel-imap-command.c line 105
#20 imap_command_start
at camel-imap-command.c line 178
#21 camel_imap_command
at camel-imap-command.c line 105
#22 imap_get_message
at camel-imap-folder.c line 1589
#23 camel_folder_get_message
at camel-folder.c line 885
#24 camel_filter_driver_filter_folder
at camel-filter-driver.c line 792
#25 filter_filter
at camel-folder.c line 1483
#26 session_thread_received
at camel-session.c line 785
#27 thread_received_msg
at e-msgport.c line 469
#28 thread_dispatch
at e-msgport.c line 550
#29 pthread_start_thread
at manager.c line 284



Unknown reporter: jplock@vasor.com, changed to bugbuddy-import@ximian.com.

Comment 1 Not Zed 2002-04-30 07:31:24 UTC

I think this is a duplicate.

A thread is doing stuff while the code underneath it has vanished.

Comment 2 Gerardo Marin 2002-04-30 16:04:48 UTC

Isn't this a slight variation of timeout_cb? (Line #11 Thread 3).

Comment 3 Jeffrey Stedfast 2002-05-21 03:21:20 UTC

yep, it's a timeout_cb bug.

Comment 4 Gerardo Marin 2002-05-21 13:36:34 UTC


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