GNOME Bugzilla – Bug 407187
[2.10] crash in em_folder_tree_model_set_folder_info at em-folder-tree-model.c:444
Last modified: 2009-09-21 10:58:30 UTC
What were you doing when the application crashed? I had just checked my MS Exchange settings in the preferences screen and clicked on 'close'. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 282779648 vsize: 0 resident: 282779648 share: 0 rss: 56913920 rss_rlim: 0 CPU usage: start_time: 1171309739 rtime: 0 utime: 3132 stime: 0 cutime:2772 cstime: 0 timeout: 360 it_real_value: 0 frequency: 13807 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233164624 (LWP 24963)] [New Thread -1433416800 (LWP 25261)] [New Thread -1388930144 (LWP 24997)] [New Thread -1398805600 (LWP 24995)] [New Thread -1390412896 (LWP 24994)] [New Thread -1380394080 (LWP 24993)] [New Thread -1371608160 (LWP 24991)] [New Thread -1363215456 (LWP 24990)] [New Thread -1354822752 (LWP 24987)] [New Thread -1301558368 (LWP 24983)] [New Thread -1292772448 (LWP 24982)] [New Thread -1283286112 (LWP 24980)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 110172
Thread 1 (Thread -1233164624 (LWP 24963))
Ubuntu bug on GNOME 2.18.0: https://launchpad.net/bugs/99818 "evolution crashes when changing the sent folder of an exchange account Binary package hint: evolution Ubuntu Feisty ProblemType: Crash Architecture: i386 Date: Sun Apr 1 18:18:46 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evolution-2.10 Package: evolution 2.10.0-0ubuntu2 ... .
+ Trace 124132
Thread 1 (process 22917)
Marking as NEW due to duplicates.
*** Bug 447797 has been marked as a duplicate of this bug. ***
*** Bug 430817 has been marked as a duplicate of this bug. ***
Bug 393505 is another possible duplicate.
Assign to Ashish.
*** Bug 469248 has been marked as a duplicate of this bug. ***
*** Bug 467081 has been marked as a duplicate of this bug. ***
*** Bug 466638 has been marked as a duplicate of this bug. ***
*** Bug 464324 has been marked as a duplicate of this bug. ***
*** Bug 463981 has been marked as a duplicate of this bug. ***
*** Bug 468058 has been marked as a duplicate of this bug. ***
*** Bug 479392 has been marked as a duplicate of this bug. ***
*** Bug 470700 has been marked as a duplicate of this bug. ***
*** Bug 472110 has been marked as a duplicate of this bug. ***
*** Bug 474485 has been marked as a duplicate of this bug. ***
*** Bug 478291 has been marked as a duplicate of this bug. ***
*** Bug 478325 has been marked as a duplicate of this bug. ***
*** Bug 479613 has been marked as a duplicate of this bug. ***
*** Bug 480283 has been marked as a duplicate of this bug. ***
*** Bug 480940 has been marked as a duplicate of this bug. ***
*** Bug 481026 has been marked as a duplicate of this bug. ***
*** Bug 481559 has been marked as a duplicate of this bug. ***
*** Bug 486959 has been marked as a duplicate of this bug. ***
*** Bug 484749 has been marked as a duplicate of this bug. ***
*** Bug 484751 has been marked as a duplicate of this bug. ***
*** Bug 485578 has been marked as a duplicate of this bug. ***
*** Bug 493073 has been marked as a duplicate of this bug. ***
*** Bug 492193 has been marked as a duplicate of this bug. ***
*** Bug 490522 has been marked as a duplicate of this bug. ***
*** Bug 487577 has been marked as a duplicate of this bug. ***
*** Bug 487320 has been marked as a duplicate of this bug. ***
*** Bug 490234 has been marked as a duplicate of this bug. ***
*** Bug 498666 has been marked as a duplicate of this bug. ***
*** Bug 498641 has been marked as a duplicate of this bug. ***
*** Bug 499612 has been marked as a duplicate of this bug. ***
*** Bug 502648 has been marked as a duplicate of this bug. ***
except from the original report here (ubuntu 6.10), all duplicates are from fedora 7 (gnome 2.18.x). there haven't been any non-fedora or fedora8 reports so far.
*** Bug 508401 has been marked as a duplicate of this bug. ***
I think this is another case of assuming the contents of a CamelFolderInfo is valid. Providers must allocate and initialize their own structs, so Evolution should not trust the contents until it's validated. Perhaps Camel should provide a supporting function for this: gboolean camel_folder_info_is_valid (CamelFolderInfo *info); But then the burden of checking falls on anything that needs folder info, and we'll forever be playing "Whack-a-Mole" with this issue. Another option is to break the API and make CamelFolderInfo an opaque struct with a sufficient API for accessing and manipulating the data. Camel would then have tighter control over the integrity of these structs. Either option is equally painful. I think making CamelFolderInfo opaque is the better long term approach, but would likely cause a ruckus in the short term. CC'ing Srini for his thoughts.
Matt, if you got some time read CamelDS. IIRC Notzed had some thoughts around this.
Everything he's describing sounds like it could be done with SQLite, but I fear it will be some time yet before I reach the depth of understanding Notzed had about the issues and tradeoffs in Camel. In the meantime, I'll just shut up and fix the crash. :)
*** Bug 511739 has been marked as a duplicate of this bug. ***
*** Bug 518163 has been marked as a duplicate of this bug. ***
*** Bug 520272 has been marked as a duplicate of this bug. ***
*** Bug 524910 has been marked as a duplicate of this bug. ***
*** Bug 506283 has been marked as a duplicate of this bug. ***
No duplicates for a few months, might be fixed.
the ubuntu submitter doesn't get the crash in the current version
Did you get similar crash any time later ? Can you please try in 2.24.x / 2.26.x and report back, thanks.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.26.3 or later), please reopen. thanks in advance.