Bug 273965 – Connector hanged when attachment of recuuring meeting modified

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 273965 - Connector hanged when attachment of recuuring meeting modified


Summary:	Connector hanged when attachment of recuuring meeting modified


Status:	RESOLVED FIXED

Product:	Evolution Exchange
Classification:	Deprecated
Component:	Connector
Version:	2.1
Hardware:	Other All

Importance:	Normal normal
Target Milestone:	reschedule
Assigned To:	Sarfraaz Ahmed
QA Contact:	Ximian Connector QA

URL:
Whiteboard:

Depends on:
Blocks:	273910

Reported:	2005-03-22 14:49 UTC by Poornima
Modified:	2005-12-08 08:30 UTC

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

Description Poornima 2005-03-22 14:49:09 UTC

Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. Sent a recurring meeting from pnayak to thanika, that had two file
attachments
2. 'pnayak' removed on attachment and sent upodates again
3. When invited user opened the meeting all the buttons in the meeting
request mail was disbaled, after sometime connector hanged

Actual Results:


Expected Results:


How often does this happen? 


Additional Information:

+ Trace 57175

#0 ??
#1 ??
#2 ??
#3 ??
#4 pthread_exit
from /lib/tls/libc.so.6
#5 g_realloc
from /opt/gnome/lib/libglib-2.0.so.0
#6 g_type_add_class_cache_func
from /opt/gnome/lib/libgobject-2.0.so.0
#7 g_type_add_class_cache_func
from /opt/gnome/lib/libgobject-2.0.so.0
#8 g_type_register_static
from /opt/gnome/lib/libgobject-2.0.so.0
#9 mail_stub_get_type
#10 mail_stub_exchange_get_type
#11 mail_stub_exchange_new
#12 exchange_component_set_offline_listener
#13 e2k_marshal_VOID__INT_INT
from /opt/gnome/lib/evolution/2.2/libexchange.so.0
#14 g_closure_invoke
from /opt/gnome/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /opt/gnome/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /opt/gnome/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /opt/gnome/lib/libgobject-2.0.so.0
#18 mail_stub_listener_construct
#19 g_io_channel_unix_get_fd
from /opt/gnome/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#21 g_main_context_acquire
from /opt/gnome/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /opt/gnome/lib/libglib-2.0.so.0
#23 bonobo_main
from /opt/gnome/lib/libbonobo-2.so.0
#24 main
#0 ??
#1 ??
#2 ??
#3 ??
#4 poll
from /lib/tls/libc.so.6
#5 g_main_context_acquire
from /opt/gnome/lib/libglib-2.0.so.0
#6 g_main_context_iteration
from /opt/gnome/lib/libglib-2.0.so.0
#7 link_main_iteration
from /opt/gnome/lib/libORBit-2.so.0
#8 giop_recv_buffer_get
from /opt/gnome/lib/libORBit-2.so.0
#9 ORBit_small_invoke_stub
from /opt/gnome/lib/libORBit-2.so.0
#10 ORBit_small_invoke_stub_n
from /opt/gnome/lib/libORBit-2.so.0
#11 ORBit_c_stub_invoke
from /opt/gnome/lib/libORBit-2.so.0
#12 GNOME_Evolution_Component_sendAndReceive
from /opt/gnome/lib/evolution/2.2/libeshell.so.0
#13 e_shell_send_receive
#14 e_shell_startup_wizard_create
#15 bonobo_ui_component_add_verb_list
from /opt/gnome/lib/libbonoboui-2.so.0
#16 g_closure_invoke
from /opt/gnome/lib/libgobject-2.0.so.0
#17 bonobo_closure_invoke_va_list
from /opt/gnome/lib/libbonobo-2.so.0
#18 bonobo_closure_invoke
from /opt/gnome/lib/libbonobo-2.so.0
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
from /usr/X11R6/lib/libX11.so.6
#26 ??
#27 ??
#28 ??
#29 _XFlushGCCache
from /usr/X11R6/lib/libX11.so.6

Comment 1 Poornima 2005-03-22 14:57:34 UTC

Happened only once

Comment 2 Sarfraaz Ahmed 2005-04-07 07:42:55 UTC

Corrupt stack. Should run once with valgrind. Lowering the priority as
this happened only once.

Comment 3 Sarfraaz Ahmed 2005-10-22 18:01:25 UTC

This should be fixed now. There was a leak in the attachment that was fixed in
2.4.1 Please verify and close this bug till you can reproduce it again.

Comment 4 Sushma Rai 2005-12-08 08:30:14 UTC

I am marking it as fixed, so that this can be triaged.