Bug 330157 – Reproducible Crash on closing Evo

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 330157 - Reproducible Crash on closing Evo


Summary:	Reproducible Crash on closing Evo


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.8.x (obsolete)
Hardware:	Other Linux

Importance:	Urgent critical
Target Milestone:	---
Assigned To:	Veerapuram Varadhan
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	272556 323138 346569 349521 354791 356156 356484 357064 358330 360099 360252 360352 362597 363681 367641 369807 371605 374568 380117 383749 387222 387902 394626 395492 395557 399159 399766 403184 403630 406088 407040 417890 423791 425483 429669 444516 451396 (view as bug list)
Depends on:
Blocks:

Reported:	2006-02-06 18:36 UTC by Karsten Bräckelmann
Modified:	2013-09-10 13:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Attachments
Proposed patch (569 bytes, patch) 2006-11-03 10:20 UTC, Srinivasa Ragavan	committed	Details \| Review

Description Karsten Bräckelmann 2006-02-06 18:36:37 UTC

On closing Evolution, it reproducibly always crashes for me.

Stacktrace generated by bug-buddy. Started Evolution, wait a few seconds till automatic check for new messages finished for my 3 IMAP accounts, closed Evo.


Backtrace was generated from '/opt/gnome-2.12/bin/evolution-2.4'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 10086)]
[New Thread -1303577680 (LWP 10099)]
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 10086)]
[New Thread -1303577680 (LWP 10099)]
[New Thread -1295184976 (LWP 10098)]
[New Thread -1278215248 (LWP 10094)]
[New Thread -1268470864 (LWP 10093)]
[New Thread -1260078160 (LWP 10091)]
[New Thread -1251292240 (LWP 10090)]
[New Thread -1242899536 (LWP 10089)]
[New Thread -1234506832 (LWP 10088)]
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 10086)]
[New Thread -1303577680 (LWP 10099)]
0xffffe410 in ?? ()

+ Trace 65952

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 libgnomeui_segv_handle
from /opt/gnome-2.12.2/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 ??
#8 folder_changed
from /opt/gnome-2.12.2/lib/libcamel-provider-1.2.so.6
#9 camel_object_trigger_event
from /opt/gnome-2.12.2/lib/libcamel-1.2.so.0
#10 vee_remove_folder
from /opt/gnome-2.12.2/lib/libcamel-provider-1.2.so.6
#11 camel_vee_folder_remove_folder
from /opt/gnome-2.12.2/lib/libcamel-provider-1.2.so.6
#12 camel_vee_folder_finalise
from /opt/gnome-2.12.2/lib/libcamel-provider-1.2.so.6
#13 camel_object_unref
from /opt/gnome-2.12.2/lib/libcamel-1.2.so.0
#14 camel_vee_folder_remove_folder
from /opt/gnome-2.12.2/lib/libcamel-provider-1.2.so.6
#15 camel_vee_folder_finalise
from /opt/gnome-2.12.2/lib/libcamel-provider-1.2.so.6
#16 camel_object_unref
from /opt/gnome-2.12.2/lib/libcamel-1.2.so.0
#17 vfolder_foreach_cb
from /opt/gnome-2.12.2/lib/evolution/2.4/components/libevolution-mail.so
#18 g_hash_table_foreach
from /opt/gnome-2.12.2/lib/libglib-2.0.so.0
#19 mail_vfolder_shutdown
from /opt/gnome-2.12.2/lib/evolution/2.4/components/libevolution-mail.so
#20 impl_quit
from /opt/gnome-2.12.2/lib/evolution/2.4/components/libevolution-mail.so
#21 _ORBIT_skel_small_GNOME_Evolution_Component_quit
from /opt/gnome-2.12.2/lib/evolution/2.4/libeshell.so.0
#22 ORBit_c_stub_invoke
from /opt/gnome-2.12.2/lib/libORBit-2.so.0
#23 GNOME_Evolution_Component_quit
from /opt/gnome-2.12.2/lib/evolution/2.4/libeshell.so.0
#24 es_run_quit
#25 e_shell_quit
#26 window_delete_event_cb
#27 _gtk_marshal_BOOLEAN__BOXED
from /opt/gnome-2.12.2/lib/libgtk-x11-2.0.so.0
#28 g_closure_invoke
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#29 signal_emit_unlocked_R
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#48 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#49 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#50 Bonobo_Unknown__classid
#51 g_param_spec_types
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#52 ORBit_TypeCode_epv
#53 g_thread_use_default_impl
#54 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#55 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#56 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#57 Bonobo_Unknown__classid
#58 g_param_spec_types
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#59 ORBit_TypeCode_epv
#60 g_thread_use_default_impl
#61 ??
#62 ??
#63 ??
#64 ??
#65 ??
#66 ??
#67 ??
#68 ??
#69 ??
#70 ??
#71 ??
#72 class_closures_cmp
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0

Comment 1 Karsten Bräckelmann 2006-02-06 18:37:18 UTC

*** Bug 323138 has been marked as a duplicate of this bug. ***

Comment 2 Karsten Bräckelmann 2006-02-06 18:39:39 UTC

This bug obsoletes my previously filed bug. Decided to create a fresh stacktrace to enable searching for the stacktrace at all.

Comment 3 Karsten Bräckelmann 2006-02-06 18:48:32 UTC

Hmm, looks like a duplicate of bug 314912.


Same stacktrace down to frame #25, e_shell_quit ().

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

Comment 4 Karsten Bräckelmann 2006-02-06 19:00:45 UTC

No, this is *not* fixed.

The fix 314912 and bug 320772 is suppsed to be in gnome-2-12 branch since 2005-11-07 (see bug 320772 comment 1). Evolution 2.4.2.1 was released on 2005-12-07, 2.4.2 on 2005-11-29.

Either the patch did not go in into gnome-2-12 branch, or this is a different issue. REOPENing. Sorry for the noise.


Cc'ing Vivek, since he seems to have worked on the other bug.

Comment 5 Karsten Bräckelmann 2006-02-06 19:12:15 UTC

Actually, removing Vivek from the Cc list again... *sigh*

Comment 6 parthasarathi susarla 2006-02-08 07:31:59 UTC

I tried reproducing this with the current build from HEAD (2.5.9) - and it seems to work fine. Not sure which patch actually fixed this - Hmm.... (me starts to check view cvs). This is going to take sometime.
Have you seen this happen on the head build guenther??

Comment 7 Karsten Bräckelmann 2006-02-11 06:09:35 UTC

Another stacktrace generated by bug-buddy, same procedure as in the original report. This time with debugging symbols.


Backtrace was generated from '/opt/gnome-2.12/bin/evolution-2.4'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 30762)]
[New Thread -1293976656 (LWP 30775)]
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 30762)]
[New Thread -1293976656 (LWP 30775)]
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 30762)]
[New Thread -1293976656 (LWP 30775)]
[New Thread -1285399632 (LWP 30774)]
[New Thread -1277006928 (LWP 30770)]
[New Thread -1268470864 (LWP 30769)]
[New Thread -1260078160 (LWP 30767)]
[New Thread -1251292240 (LWP 30766)]
[New Thread -1242899536 (LWP 30765)]
[New Thread -1234506832 (LWP 30764)]
0xffffe410 in ?? ()

+ Trace 66085

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 libgnomeui_segv_handle
from /opt/gnome-2.12.2/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 ??
#8 folder_changed
at camel-vee-folder.c line 1457
#9 camel_object_trigger_event
at camel-object.c line 1502
#10 vee_remove_folder
at camel-vee-folder.c line 831
#11 camel_vee_folder_remove_folder
at camel-vee-folder.c line 296
#12 camel_vee_folder_finalise
at camel-vee-folder.c line 1723
#13 camel_object_unref
at camel-object.c line 925
#14 camel_vee_folder_remove_folder
at camel-vee-folder.c line 298
#15 camel_vee_folder_finalise
at camel-vee-folder.c line 1723
#16 camel_object_unref
at camel-object.c line 925
#17 vfolder_foreach_cb
at mail-vfolder.c line 1178
#18 g_hash_table_foreach
from /opt/gnome-2.12.2/lib/libglib-2.0.so.0
#19 mail_vfolder_shutdown
at mail-vfolder.c line 1188
#20 impl_quit
at mail-component.c line 723
#21 _ORBIT_skel_small_GNOME_Evolution_Component_quit
at Evolution-common.c line 32
#22 ORBit_c_stub_invoke
from /opt/gnome-2.12.2/lib/libORBit-2.so.0
#23 GNOME_Evolution_Component_quit
at Evolution-stubs.c line 41
#24 es_run_quit
at e-shell.c line 1293
#25 e_shell_quit
at e-shell.c line 1361
#26 window_delete_event_cb
at e-shell.c line 343
#27 _gtk_marshal_BOOLEAN__BOXED
from /opt/gnome-2.12.2/lib/libgtk-x11-2.0.so.0
#28 g_closure_invoke
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#29 signal_emit_unlocked_R
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#48 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#49 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#50 Bonobo_Unknown__classid
#51 g_param_spec_types
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#52 ORBit_TypeCode_epv
#53 g_thread_use_default_impl
#54 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#55 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#56 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#57 Bonobo_Unknown__classid
#58 g_param_spec_types
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#59 ORBit_TypeCode_epv
#60 g_thread_use_default_impl
#61 ??
#62 ??
#63 ??
#64 ??
#65 ??
#66 ??
#67 ??
#68 ??
#69 ??
#70 ??
#71 ??
#72 class_closures_cmp
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0

Comment 8 Karsten Bräckelmann 2006-02-11 06:24:21 UTC

Partha: I didn't really use HEAD builds yet.

Anyway, there is another "crashes on close" bug out there I commented on, which might be related. See bug 272556 comment 29:
> IIRC Evo did not crash for me on closing, after setting up a fresh one. At
> some point later, it started to, again. I believe I have went though this
> more than once already...

This might be the same reason. I don't know. Fact is, I previously noticed a reprodicuble crash on exit, which was no issue at some point later. Most likely when starting fresh. Not sure. But it always started to crash later on...

Thus I am not surprised that you can not reproduce this... *sigh*


Need to do some more testing. Feel free to poke me on IRC. Meanwhile, have fun with the fresh stacktrace. :)

Comment 9 Karsten Bräckelmann 2006-02-12 21:16:03 UTC

Another trace, same steps as previously. Evolution and e-d-s built with no custom CFLAGS for optimization this time, debugging symbols enabled. As vanilla as can be.


Backtrace was generated from '/opt/gnome-2.12/bin/evolution-2.4'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229859136 (LWP 22829)]
[New Thread -1287816272 (LWP 22894)]
[Thread debugging using libthread_db enabled]
[New Thread -1229859136 (LWP 22829)]
[New Thread -1287816272 (LWP 22894)]
[Thread debugging using libthread_db enabled]
[New Thread -1229859136 (LWP 22829)]
[New Thread -1287816272 (LWP 22894)]
[New Thread -1279423568 (LWP 22893)]
[New Thread -1270887504 (LWP 22839)]
[New Thread -1262490704 (LWP 22837)]
[New Thread -1254098000 (LWP 22836)]
[New Thread -1243522128 (LWP 22835)]
[New Thread -1235129424 (LWP 22834)]
0xffffe410 in ?? ()

+ Trace 66116

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 libgnomeui_segv_handle
from /opt/gnome-2.12.2/lib/libgnomeui-2.so.0
#6 segv_redirect
at main.c line 424
#7 <signal handler called>
#8 ??
#9 folder_changed
at camel-vee-folder.c line 1457
#10 camel_object_trigger_event
at camel-object.c line 1502
#11 vee_folder_remove_folder
at camel-vee-folder.c line 831
#12 vee_remove_folder
at camel-vee-folder.c line 1607
#13 camel_vee_folder_remove_folder
at camel-vee-folder.c line 296
#14 camel_vee_folder_finalise
at camel-vee-folder.c line 1723
#15 camel_object_unref
at camel-object.c line 925
#16 camel_vee_folder_remove_folder
at camel-vee-folder.c line 298
#17 camel_vee_folder_finalise
at camel-vee-folder.c line 1723
#18 camel_object_unref
at camel-object.c line 925
#19 vfolder_foreach_cb
at mail-vfolder.c line 1178
#20 g_hash_table_foreach
from /opt/gnome-2.12.2/lib/libglib-2.0.so.0
#21 mail_vfolder_shutdown
at mail-vfolder.c line 1188
#22 impl_quit
at mail-component.c line 723
#23 _ORBIT_skel_small_GNOME_Evolution_Component_quit
at Evolution-common.c line 32
#24 ORBit_c_stub_invoke
from /opt/gnome-2.12.2/lib/libORBit-2.so.0
#25 GNOME_Evolution_Component_quit
at Evolution-stubs.c line 41
#26 es_run_quit
at e-shell.c line 1293
#27 e_shell_quit
at e-shell.c line 1361
#28 e_shell_request_close_window
at e-shell.c line 962
#29 window_delete_event_cb
at e-shell.c line 343
#30 _gtk_marshal_BOOLEAN__BOXED
from /opt/gnome-2.12.2/lib/libgtk-x11-2.0.so.0
#31 g_closure_invoke
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#32 signal_emit_unlocked_R
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
#50 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#51 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#52 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#53 Bonobo_Unknown__classid
#54 g_param_spec_types
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#55 ORBit_TypeCode_epv
#56 g_thread_use_default_impl
#57 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#58 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#59 __PRETTY_FUNCTION__.0
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#60 Bonobo_Unknown__classid
#61 g_param_spec_types
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#62 ORBit_TypeCode_epv
#63 g_thread_use_default_impl
#64 ??
#65 ??
#66 ??
#67 ??
#68 ??
#69 ??
#70 ??
#71 ??
#72 ??
#73 ??
#74 ??
#75 class_closures_cmp
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0

Comment 10 parthasarathi susarla 2006-02-16 10:27:38 UTC

its a crash for sure - but am not able to reproduce this at all. Sigh!

Comment 11 Karsten Bräckelmann 2006-02-18 23:06:57 UTC

See comment 8. I already told you, dude...

What else do you need beside a plain vanilla stacktrace with debugging symbols?
btw, the same with 2.5.91.

Comment 12 Karsten Bräckelmann 2006-02-24 20:23:18 UTC

Additional note: Evo crashes only, if the Mailer was used, i.e. I opened the Mailer component. (All IMAP accounts are configured to periodically and automatically check for new mail.)

If I start Evo, only use the Address Book, and close Evo after that, I do not get this crash.

Still, it crashes always on close, when I switched to the Mailer component.

Comment 13 André Klapper 2006-06-17 14:57:10 UTC

guenther, any news on this? still reproducible? guess so, code has not changed in the last six months...

partha:

+ Trace 68897

#9 folder_changed
at camel-vee-folder.c line 1457


retargetting.

Comment 14 Karsten Bräckelmann 2006-07-04 17:46:13 UTC

Andre, didn't have a look at fresh stacktraces in a while, but the issue did not change at all.  Perfectly reproducible crash.

Please see all the details I mentioned above. The stacktrace is identical to others (which are closed as fixed), but this crash is *NOT* fixed.

Comment 15 Karsten Bräckelmann 2006-07-04 17:50:11 UTC

*** Bug 346569 has been marked as a duplicate of this bug. ***

Comment 16 Karsten Bräckelmann 2006-07-04 17:52:31 UTC

See duplicate bug 346569 -- *still* an issue with 2.6.x.

Comment 17 Guille -bisho- 2006-07-04 18:04:13 UTC

Sorry for tge dupped bug 346569. If you need any other trace or something to check this, please ask. I will be glad to help.

Comment 18 Harish Krishnaswamy 2006-08-10 12:59:57 UTC

Set target milestone to 2.8

Comment 19 Daniel Holbach 2006-08-30 14:43:31 UTC

https://launchpad.net/distros/ubuntu/+source/evolution/+bug/57975 has a similar backtrace.

Comment 20 Rob Bradford 2006-09-08 15:46:01 UTC

*** Bug 354791 has been marked as a duplicate of this bug. ***

Comment 21 André Klapper 2006-09-17 16:04:39 UTC

*** Bug 356156 has been marked as a duplicate of this bug. ***

Comment 22 André Klapper 2006-09-17 16:04:59 UTC

varadhan: stacktrace with uptodate line numbers available at bug 356156

Comment 23 Karsten Bräckelmann 2006-09-18 19:50:17 UTC

*** Bug 356484 has been marked as a duplicate of this bug. ***

Comment 24 Sebastien Bacher 2006-09-19 07:22:50 UTC

The Ubuntu bug submitter stated it's fixed for him with evolution 2.8.0

Comment 25 Karsten Bräckelmann 2006-09-19 20:14:00 UTC

*** Bug 349521 has been marked as a duplicate of this bug. ***

Comment 26 André Klapper 2006-09-25 19:27:24 UTC

up to date stacktrace with symbols available at bug 357064

Comment 27 André Klapper 2006-09-25 19:27:33 UTC

*** Bug 357064 has been marked as a duplicate of this bug. ***

Comment 28 André Klapper 2006-09-29 16:02:07 UTC

*** Bug 358330 has been marked as a duplicate of this bug. ***

Comment 29 André Klapper 2006-10-06 08:18:44 UTC

bug 360099 provides an up-to-date stacktrace with line numbers. this is getting urgent as we get more and more duplicates.

Comment 30 André Klapper 2006-10-06 08:18:54 UTC

*** Bug 360099 has been marked as a duplicate of this bug. ***

Comment 31 André Klapper 2006-10-06 19:39:25 UTC

*** Bug 360252 has been marked as a duplicate of this bug. ***

Comment 32 Elijah Newren 2006-10-07 15:37:35 UTC

*** Bug 360352 has been marked as a duplicate of this bug. ***

Comment 33 Elijah Newren 2006-10-07 15:38:17 UTC

bug 360352 has a stack trace with line numbers that might be newer...

Comment 34 Rob Bradford 2006-10-16 13:17:16 UTC

*** Bug 362597 has been marked as a duplicate of this bug. ***

Comment 35 parthasarathi susarla 2006-10-20 03:50:44 UTC

related to bug 316071

Comment 36 Karsten Bräckelmann 2006-10-20 14:56:52 UTC

*** Bug 363681 has been marked as a duplicate of this bug. ***

Comment 37 Karsten Bräckelmann 2006-10-30 19:31:01 UTC

*** Bug 367641 has been marked as a duplicate of this bug. ***

Comment 38 Daniel Holbach 2006-10-31 17:23:11 UTC

https://launchpad.net/distros/ubuntu/+source/evolution/+bug/57975/comments/16 has another backtrace with evo symbols.

Comment 39 Srinivasa Ragavan 2006-11-03 10:20:59 UTC

Created attachment 75922 [details] [review]
Proposed patch

Comment 40 Srinivasa Ragavan 2006-11-03 10:29:38 UTC

I have tried this patch and it works perfectly and Im not able to see the crash at all. I have reproduced this in the following scenario continuously.

If your search folder structure looks like below

----------------
> FOOACCOUNT
  - INBOX
  - FOOBOX

>Search Folders

  - Foo
  - Baa
  - Foo123
  - Baa123
  - Unmatched
-----------------------

1. Create Foo123 in a way that the sources for this vfolder are INBOX and Foo (search Folder).

2. Have the focus in Baa and close you can see this crash continuously. If you have the focus in Foo123 or Foo, this crash wont occur.

The reason for the crash is that when a VFolder is a source/sub to a VFolder, the refcounts arenot handled right. When the source/sub folders of a VFOlder are unreffed, I decided to unref the source/sub only if it is not a vfolder. There could be other ways to fix this bug also, leaving this as a work around. I would let the maintainer, review and decide on it. Thx.

Comment 41 parthasarathi susarla 2006-11-03 14:53:39 UTC

The patch targets the problem. But i'm not sure if just this would end up fixing the problem. 
The issue is that there are unrefs on an object which has its ref count set to 0. I'm not able to trace down the exact path. Fixed a few unref issues but still no where close to fixing the complete issue. 

But yes, the patch from srini surely is a hack.

Comment 42 Jeremiah Poling 2006-11-03 15:15:52 UTC

*** Bug 369807 has been marked as a duplicate of this bug. ***

Comment 43 Srinivasa Ragavan 2006-11-06 05:47:00 UTC

Partha, it fixes the bug. It doesnt have any side effect, not even a leak. I'll commit the patch for now as it is annoying to have a crash on shutdown 100% all the times.

Comment 44 Srinivasa Ragavan 2006-11-06 05:53:32 UTC

Committed to HEAD and Stable. We can look at a better fix as we go on. Thanks.

Comment 45 Karsten Bräckelmann 2006-11-06 23:37:50 UTC

*** Bug 371605 has been marked as a duplicate of this bug. ***

Comment 46 André Klapper 2006-11-13 11:30:18 UTC

*** Bug 374568 has been marked as a duplicate of this bug. ***

Comment 47 Veerapuram Varadhan 2006-11-14 07:19:07 UTC

*** Bug 272556 has been marked as a duplicate of this bug. ***

Comment 48 Mikael Nilsson 2006-12-08 17:26:17 UTC

Running 2.9.3 in Ubuntu Feisty, I no longer see this issue. Thanks!

Comment 49 André Klapper 2006-12-10 16:19:04 UTC

*** Bug 383749 has been marked as a duplicate of this bug. ***

Comment 50 André Klapper 2006-12-10 16:19:32 UTC

*** Bug 380117 has been marked as a duplicate of this bug. ***

Comment 51 palfrey 2007-01-09 23:24:21 UTC

*** Bug 387222 has been marked as a duplicate of this bug. ***

Comment 52 palfrey 2007-01-09 23:24:30 UTC

*** Bug 387902 has been marked as a duplicate of this bug. ***

Comment 53 palfrey 2007-01-09 23:24:40 UTC

*** Bug 394626 has been marked as a duplicate of this bug. ***

Comment 54 palfrey 2007-01-12 12:03:08 UTC

*** Bug 395557 has been marked as a duplicate of this bug. ***

Comment 55 palfrey 2007-01-12 12:03:11 UTC

*** Bug 395492 has been marked as a duplicate of this bug. ***

Comment 56 palfrey 2007-01-22 12:56:31 UTC

*** Bug 399159 has been marked as a duplicate of this bug. ***

Comment 57 palfrey 2007-01-23 14:06:40 UTC

*** Bug 399766 has been marked as a duplicate of this bug. ***

Comment 58 palfrey 2007-02-01 13:01:33 UTC

*** Bug 403184 has been marked as a duplicate of this bug. ***

Comment 59 palfrey 2007-02-03 11:52:04 UTC

*** Bug 403630 has been marked as a duplicate of this bug. ***

Comment 60 André Klapper 2007-02-16 23:47:15 UTC

*** Bug 407040 has been marked as a duplicate of this bug. ***

Comment 61 André Klapper 2007-02-16 23:47:22 UTC

*** Bug 406088 has been marked as a duplicate of this bug. ***

Comment 62 André Klapper 2007-03-17 19:56:13 UTC

*** Bug 417890 has been marked as a duplicate of this bug. ***

Comment 63 Akhil Laddha 2007-04-03 04:19:35 UTC

*** Bug 425483 has been marked as a duplicate of this bug. ***

Comment 64 André Klapper 2007-04-12 20:48:52 UTC

*** Bug 423791 has been marked as a duplicate of this bug. ***

Comment 65 palfrey 2007-04-26 14:09:34 UTC

*** Bug 429669 has been marked as a duplicate of this bug. ***

Comment 66 palfrey 2007-06-06 10:31:46 UTC

*** Bug 444516 has been marked as a duplicate of this bug. ***

Comment 67 palfrey 2007-06-27 13:35:34 UTC

*** Bug 451396 has been marked as a duplicate of this bug. ***