GNOME Bugzilla – Bug 339602
crash in camel_index_add_name() at camel-index.c:183
Last modified: 2013-09-10 13:42:36 UTC
Distribution: Red Hat Enterprise Linux AS release 4 (Nahant Update 2) Package: Evolution Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Evolution crashed not long after startup, maybe due to enabling plugin Bugzilla-Product: Evolution Bugzilla-Component: Shell Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: I had just started evolution and it was (VERY SLOWLY) doing something, but had not yet shown me the mail in my local inbox (my inbox has about a thousand msgs, and evolution was taking 99% CPU, so I theorize it was doing something there). I was poking around and clicked on the Plugins menu item. The only unchecked plugin was the Exchange plugin, and I use Exchange, so I enabled it, clicked OK, and Evo crashed. Hard to say whether it was in response to the plugin or just a similar bug soon after startup that I reported about 2 minutes ago. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.6' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208133952 (LWP 6934)] [New Thread -1327498320 (LWP 6997)] [New Thread -1296606288 (LWP 6970)] [New Thread -1285723216 (LWP 6969)] [New Thread -1275233360 (LWP 6968)] [New Thread -1264743504 (LWP 6967)] [New Thread -1254253648 (LWP 6947)] [New Thread -1243616336 (LWP 6946)] [New Thread -1233126480 (LWP 6944)] [New Thread -1221100624 (LWP 6945)] [New Thread -1210610768 (LWP 6942)] 0x002517a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 67818
Thread 8 (Thread -1243616336 (LWP 6946))
------- Bug created by bug-buddy at 2006-04-24 16:53 -------
I may be hitting the same bug. When I closed Evo I hit the familiar bug of "i'm greyed and take forever to close while using massive CPU". It finally closed and on restart I get a LONG "Storing folder..." before anything updates, also a familiar annoyance. It gets about 75% of the way through "Storing folder" and I get this crash. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1297089616 (LWP 13623)] 0xb6e2113d in camel_index_add_name (idx=0x0, name=0x0) at camel-index.c:183 183 camel-index.c: No such file or directory. in camel-index.c (gdb) thread apply all bt
+ Trace 68235
Thread 9 (Thread -1297089616 (LWP 13623))
Thread 2 (Thread -1242571856 (LWP 13609))
*** This bug has been marked as a duplicate of 339600 ***
Um, I hit this with 2.6.1 - 339600 is marked RESOLVED OBSOLETE.
Hmm, according to the stacktrace, I don't think this is a duplicate of bug 339600. REOPENing.
*** Bug 353730 has been marked as a duplicate of this bug. ***
> Backtrace was generated from '/usr/bin/evolution-2.6' Original report filed against 2.6.x Stacktrace in comment 1 also using 2.6.x Duplicate using 2.7.x Sure not obsolete. ;) Hmm, now I wonder if the stacktrace in comment 1 really is the same bug as the original report...
(In reply to comment #1) > I may be hitting the same bug. Lee, according to the stacktrace, this is not the same issue as the original report. Bug 353730 is, so you might want to watch that one.
Similar stacktrace obtained on evolution 2.8.0 + e-d-s 1.8.0 : This is on a system with Maildir account : after a crash for another problem, evolution crashes at startup, while reconstructing its summary files. There is because of race condition in folder summary for Maildir, when summary reindexing get perturbed by new mail arrival => another thread try to disable indexing while indexing is already in progress, causing the crash. To fix this crash, I think we need to add a lock in camel_folder_summary_set_index (probaby on filter_lock) but I'm not a camel expert with deep code knownledge. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1260254304 (LWP 25241)] camel_index_add_name (idx=0x0, name=0xb177e288 "1141212934.9054_0.trinidad.mandrakesoft.com") at camel-index.c:183 183 if ((idx->state & CAMEL_INDEX_DELETED) == 0) (gdb) thread apply all bt
+ Trace 72922
Thread 3 (Thread -1260254304 (LWP 25241))
I'm pretty sure that I have evolution using mbox and I've just had the same issues. (I'll file my backtrace in at the bottom of the posting.). I turned off my network connection and started evolution and it got through the "Storing folder (???% complete) stage successfully (it had been crashing at around 60% to 70% of the way through storing). It appears that evolutionns attempt to get mail while it's trying to "storing folders..." conflicts and caused a crash. So turing off the network stopped evolution trying to get mail on start and evolution is now working for me. Thanks to Andre in #evolution for all his help figuring this out. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled ----------- .xsession-errors (2507 sec old) --------------------- (evolution:9571): camel-WARNING **: Could not create key entry for word 'configuring': Interrupted system call (evolution:9571): camel-WARNING **: Could not create key entry for word 'glued': Interrupted system call (evolution:9571): camel-WARNING **: Could not create key entry for word 'programming': Interrupted system call (evolution:9571): camel-WARNING **: Could not create key entry for word 'pundits': Interrupted system call (evolution:9571) ...Too much output, ignoring rest... -------------------------------------------------- Memory status: size: 145240064 vsize: 0 resident: 145240064 share: 0 rss: 42835968 rss_rlim: 0 CPU usage: start_time: 1169081286 rtime: 0 utime: 6791 stime: 0 cutime:5574 cstime: 0 timeout: 1217 it_real_value: 0 frequency: 2 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208309536 (LWP 10336)] [New Thread -1292412016 (LWP 10381)] [New Thread -1281922160 (LWP 10380)] [New Thread -1271039088 (LWP 10379)] [New Thread -1250976880 (LWP 10375)] [New Thread -1240487024 (LWP 10374)] [New Thread -1229599856 (LWP 10373)] [New Thread -1219110000 (LWP 10370)] 0x003cd402 in __kernel_vsyscall ()
+ Trace 103134
Thread 8 (Thread -1219110000 (LWP 10370))
Similar backtrace at https://beta.launchpad.net/ubuntu/+source/evolution/+bug/94766
+ Trace 121478
*** Bug 371529 has been marked as a duplicate of this bug. ***
*** Bug 410345 has been marked as a duplicate of this bug. ***
*** Bug 446387 has been marked as a duplicate of this bug. ***
*** Bug 446500 has been marked as a duplicate of this bug. ***
*** Bug 447432 has been marked as a duplicate of this bug. ***
*** Bug 447044 has been marked as a duplicate of this bug. ***
*** Bug 449749 has been marked as a duplicate of this bug. ***
*** Bug 324509 has been marked as a duplicate of this bug. ***
*** Bug 452118 has been marked as a duplicate of this bug. ***
*** Bug 454240 has been marked as a duplicate of this bug. ***
*** Bug 331923 has been marked as a duplicate of this bug. ***
*** Bug 357947 has been marked as a duplicate of this bug. ***
*** Bug 362788 has been marked as a duplicate of this bug. ***
*** Bug 430794 has been marked as a duplicate of this bug. ***
*** Bug 448935 has been marked as a duplicate of this bug. ***
*** Bug 448938 has been marked as a duplicate of this bug. ***
*** Bug 450673 has been marked as a duplicate of this bug. ***
*** Bug 458331 has been marked as a duplicate of this bug. ***
*** Bug 457411 has been marked as a duplicate of this bug. ***
*** Bug 456873 has been marked as a duplicate of this bug. ***
*** Bug 456003 has been marked as a duplicate of this bug. ***
*** Bug 455339 has been marked as a duplicate of this bug. ***
*** Bug 450945 has been marked as a duplicate of this bug. ***
*** Bug 452116 has been marked as a duplicate of this bug. ***
*** Bug 452114 has been marked as a duplicate of this bug. ***
*** Bug 451714 has been marked as a duplicate of this bug. ***
*** Bug 451404 has been marked as a duplicate of this bug. ***
*** Bug 459405 has been marked as a duplicate of this bug. ***
*** Bug 459350 has been marked as a duplicate of this bug. ***
*** Bug 458723 has been marked as a duplicate of this bug. ***
*** Bug 459701 has been marked as a duplicate of this bug. ***
bug 450669 could be another dup
*** Bug 450669 has been marked as a duplicate of this bug. ***
Hello. This morning I have got 25 messages from bugzilla due to this bug. Is it that I receive a mail every time someone sent a crash report on this bug mailing list? Note that I have had not so many crash, and I do not send anymore crash reports (as the info are the same of the first). Or is this another bug itself? Matteo
@matteo: at the bottom of those 25 messages you can read the following: "See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system."
*** Bug 460839 has been marked as a duplicate of this bug. ***
*** Bug 460840 has been marked as a duplicate of this bug. ***
*** Bug 461153 has been marked as a duplicate of this bug. ***
*** Bug 461170 has been marked as a duplicate of this bug. ***
*** Bug 461389 has been marked as a duplicate of this bug. ***
*** Bug 461390 has been marked as a duplicate of this bug. ***
*** Bug 461993 has been marked as a duplicate of this bug. ***
*** Bug 460883 has been marked as a duplicate of this bug. ***
Can confirm comment 9 and probably comment 8. Just came across a report on IRC (stacktrace looked like it is this issue), description about storing folder matches. POP3 account. Also, mail has been fetched when the crash occured. Workaround: Start Evolution in Offline mode from a terminal, running the command 'evolution --offline'. Wait, till the "storing folder ..." info disappears from the status bar. [1] After that, switch to Online mode (File / Work Online) and fetch your mail hitting the Send/Receive button. (Note: We tried something else before, which might be related even though I doubt it. Anyway, for completeness: Started 'evolution --component=calendar' to not get to the Mailer. Edit the POP3 account prefernces, and disable periodically fetching for mail, if enabled. Switch to Offline mode.) [1] View / Status Bar to get the bottom status bar if it s disabled
*** Bug 463436 has been marked as a duplicate of this bug. ***
Created attachment 93774 [details] [review] idx check if it is null Just check this patch.
Comment on attachment 93774 [details] [review] idx check if it is null The line before your extra check is: g_return_val_if_fail (CAMEL_IS_INDEX (idx), FALSE); This causes the function to return if idx is NULL.
*** Bug 463230 has been marked as a duplicate of this bug. ***
*** Bug 463559 has been marked as a duplicate of this bug. ***
*** Bug 463580 has been marked as a duplicate of this bug. ***
*** Bug 463721 has been marked as a duplicate of this bug. ***
*** Bug 464022 has been marked as a duplicate of this bug. ***
*** Bug 464024 has been marked as a duplicate of this bug. ***
*** Bug 464025 has been marked as a duplicate of this bug. ***
*** Bug 464052 has been marked as a duplicate of this bug. ***
*** Bug 464167 has been marked as a duplicate of this bug. ***
*** Bug 466713 has been marked as a duplicate of this bug. ***
*** Bug 466984 has been marked as a duplicate of this bug. ***
*** Bug 467508 has been marked as a duplicate of this bug. ***
*** Bug 467509 has been marked as a duplicate of this bug. ***
Ross added an argument check to camel_index_add_name() in bug #460861 so that the function will return NULL and print a warning to stderr instead of crash. I imagine there's a deeper issue at work here that's causing "idx" to be NULL in the first place, but this particular crash should be fixed now. Is that sufficient to close this bug?
@ reporters: if anybody of you can reproduce this issue with an evolution-data-server version later than 1.11.6, please reopen this bug report. note that the 1.11.x series are unstable testing releases and that the stable 1.12.x series (included in GNOME 2.20) will be available in exactly one month. thanks in advance for your help! @matthew: oh cool, so you found some time to investigate after bathing your cat. yeah, closing then. ;-)
*** Bug 469107 has been marked as a duplicate of this bug. ***
Is this similar of http://bugzilla.gnome.org/show_bug.cgi?id=339602
*** Bug 468950 has been marked as a duplicate of this bug. ***
*** Bug 471693 has been marked as a duplicate of this bug. ***
*** Bug 469624 has been marked as a duplicate of this bug. ***
*** Bug 471922 has been marked as a duplicate of this bug. ***
(In reply to comment #71) > I imagine there's a deeper issue at work here that's causing "idx" to be NULL > in the first place, but this particular crash should be fixed now. > > Is that sufficient to close this bug? > I'd say, it's not, since.the issue itself hasn't been resolved yet. One could lower severity as it shouldn't crash immediately and lower priority as there are more important crashers though.
*** Bug 480092 has been marked as a duplicate of this bug. ***
*** Bug 469795 has been marked as a duplicate of this bug. ***
*** Bug 475025 has been marked as a duplicate of this bug. ***
*** Bug 476603 has been marked as a duplicate of this bug. ***
*** Bug 476604 has been marked as a duplicate of this bug. ***
*** Bug 478320 has been marked as a duplicate of this bug. ***
*** Bug 478357 has been marked as a duplicate of this bug. ***
*** Bug 478419 has been marked as a duplicate of this bug. ***
*** Bug 478421 has been marked as a duplicate of this bug. ***
*** Bug 478606 has been marked as a duplicate of this bug. ***
*** Bug 478424 has been marked as a duplicate of this bug. ***
*** Bug 480228 has been marked as a duplicate of this bug. ***
*** Bug 480515 has been marked as a duplicate of this bug. ***
*** Bug 481017 has been marked as a duplicate of this bug. ***
*** Bug 470267 has been marked as a duplicate of this bug. ***
*** Bug 473248 has been marked as a duplicate of this bug. ***
*** Bug 474448 has been marked as a duplicate of this bug. ***
*** Bug 474752 has been marked as a duplicate of this bug. ***
*** Bug 474892 has been marked as a duplicate of this bug. ***
*** Bug 476889 has been marked as a duplicate of this bug. ***
*** Bug 477882 has been marked as a duplicate of this bug. ***
*** Bug 477883 has been marked as a duplicate of this bug. ***
*** Bug 478279 has been marked as a duplicate of this bug. ***
*** Bug 478559 has been marked as a duplicate of this bug. ***
*** Bug 480454 has been marked as a duplicate of this bug. ***
*** Bug 481408 has been marked as a duplicate of this bug. ***
*** Bug 479728 has been marked as a duplicate of this bug. ***
*** Bug 481923 has been marked as a duplicate of this bug. ***
*** Bug 481982 has been marked as a duplicate of this bug. ***
*** Bug 482117 has been marked as a duplicate of this bug. ***
*** Bug 483581 has been marked as a duplicate of this bug. ***
*** Bug 483583 has been marked as a duplicate of this bug. ***
*** Bug 484098 has been marked as a duplicate of this bug. ***
*** Bug 482547 has been marked as a duplicate of this bug. ***
*** Bug 484324 has been marked as a duplicate of this bug. ***
*** Bug 471003 has been marked as a duplicate of this bug. ***
(In reply to comment #72) > @ reporters: if anybody of you can reproduce this issue with an > evolution-data-server version later than 1.11.6, please reopen this bug report. > hm. bug 471003 is on Evo 2.12 and I can't derive the version from "/usr/lib/libcamel-1.2.so.10". So you might want to reopen this bug. But according to comment #79 we should do so anyway.
*** Bug 472463 has been marked as a duplicate of this bug. ***
*** Bug 472465 has been marked as a duplicate of this bug. ***
*** Bug 474990 has been marked as a duplicate of this bug. ***
*** Bug 484598 has been marked as a duplicate of this bug. ***
*** Bug 484599 has been marked as a duplicate of this bug. ***
*** Bug 484777 has been marked as a duplicate of this bug. ***
*** Bug 485245 has been marked as a duplicate of this bug. ***
*** Bug 485164 has been marked as a duplicate of this bug. ***
*** Bug 485630 has been marked as a duplicate of this bug. ***
*** Bug 485629 has been marked as a duplicate of this bug. ***
*** Bug 485631 has been marked as a duplicate of this bug. ***
*** Bug 485632 has been marked as a duplicate of this bug. ***
*** Bug 485781 has been marked as a duplicate of this bug. ***
weird. after trying the "run offline and then go online" suggestion it's now working all the time - even if i start evo online! do you think that's what comment #9 (and comment #54) meant? last evo update was 2.10.3-4.fc7 on 12 sep 07. last eds update was 1.10.3.1-2.fc7 on 27 jul 07. last glibc update was 2.6-4 on 13 jul 07.
*** Bug 486561 has been marked as a duplicate of this bug. ***
*** Bug 487081 has been marked as a duplicate of this bug. ***
*** Bug 487225 has been marked as a duplicate of this bug. ***
*** Bug 487316 has been marked as a duplicate of this bug. ***
*** Bug 487421 has been marked as a duplicate of this bug. ***
*** Bug 487422 has been marked as a duplicate of this bug. ***
*** Bug 487447 has been marked as a duplicate of this bug. ***
*** Bug 487527 has been marked as a duplicate of this bug. ***
*** Bug 487984 has been marked as a duplicate of this bug. ***
*** Bug 487985 has been marked as a duplicate of this bug. ***
*** Bug 487986 has been marked as a duplicate of this bug. ***
*** Bug 488084 has been marked as a duplicate of this bug. ***
*** Bug 488085 has been marked as a duplicate of this bug. ***
*** Bug 488424 has been marked as a duplicate of this bug. ***
*** Bug 488643 has been marked as a duplicate of this bug. ***
*** Bug 488176 has been marked as a duplicate of this bug. ***
*** Bug 488954 has been marked as a duplicate of this bug. ***
*** Bug 489224 has been marked as a duplicate of this bug. ***
*** Bug 487971 has been marked as a duplicate of this bug. ***
*** Bug 489434 has been marked as a duplicate of this bug. ***
*** Bug 489411 has been marked as a duplicate of this bug. ***
*** Bug 489408 has been marked as a duplicate of this bug. ***
*** Bug 489579 has been marked as a duplicate of this bug. ***
*** Bug 490498 has been marked as a duplicate of this bug. ***
*** Bug 490639 has been marked as a duplicate of this bug. ***
*** Bug 491280 has been marked as a duplicate of this bug. ***
*** Bug 491290 has been marked as a duplicate of this bug. ***
*** Bug 491353 has been marked as a duplicate of this bug. ***
*** Bug 491379 has been marked as a duplicate of this bug. ***
*** Bug 491330 has been marked as a duplicate of this bug. ***
*** Bug 491382 has been marked as a duplicate of this bug. ***
*** Bug 491395 has been marked as a duplicate of this bug. ***
*** Bug 491398 has been marked as a duplicate of this bug. ***
*** Bug 491284 has been marked as a duplicate of this bug. ***
*** Bug 491635 has been marked as a duplicate of this bug. ***
*** Bug 491714 has been marked as a duplicate of this bug. ***
*** Bug 491727 has been marked as a duplicate of this bug. ***
*** Bug 491738 has been marked as a duplicate of this bug. ***
*** Bug 491735 has been marked as a duplicate of this bug. ***
*** Bug 491745 has been marked as a duplicate of this bug. ***
*** Bug 491866 has been marked as a duplicate of this bug. ***
*** Bug 491951 has been marked as a duplicate of this bug. ***
*** Bug 491937 has been marked as a duplicate of this bug. ***
*** Bug 492543 has been marked as a duplicate of this bug. ***
*** Bug 492522 has been marked as a duplicate of this bug. ***
*** Bug 493555 has been marked as a duplicate of this bug. ***
*** Bug 493676 has been marked as a duplicate of this bug. ***
*** Bug 493269 has been marked as a duplicate of this bug. ***
*** Bug 493991 has been marked as a duplicate of this bug. ***
*** Bug 496417 has been marked as a duplicate of this bug. ***
*** Bug 496173 has been marked as a duplicate of this bug. ***
*** Bug 498129 has been marked as a duplicate of this bug. ***
*** Bug 498726 has been marked as a duplicate of this bug. ***
*** Bug 498903 has been marked as a duplicate of this bug. ***
*** Bug 498865 has been marked as a duplicate of this bug. ***
*** Bug 498993 has been marked as a duplicate of this bug. ***
*** Bug 499579 has been marked as a duplicate of this bug. ***
*** Bug 499988 has been marked as a duplicate of this bug. ***
*** Bug 499991 has been marked as a duplicate of this bug. ***
*** Bug 500418 has been marked as a duplicate of this bug. ***
*** Bug 500417 has been marked as a duplicate of this bug. ***
*** Bug 500480 has been marked as a duplicate of this bug. ***
*** Bug 500732 has been marked as a duplicate of this bug. ***
*** Bug 502305 has been marked as a duplicate of this bug. ***
*** Bug 502585 has been marked as a duplicate of this bug. ***
*** Bug 502551 has been marked as a duplicate of this bug. ***
*** Bug 502562 has been marked as a duplicate of this bug. ***
*** Bug 502828 has been marked as a duplicate of this bug. ***
*** Bug 503104 has been marked as a duplicate of this bug. ***
*** Bug 503833 has been marked as a duplicate of this bug. ***
*** Bug 503835 has been marked as a duplicate of this bug. ***
*** Bug 504194 has been marked as a duplicate of this bug. ***
*** Bug 504159 has been marked as a duplicate of this bug. ***
*** Bug 505725 has been marked as a duplicate of this bug. ***
*** Bug 505850 has been marked as a duplicate of this bug. ***
*** Bug 505838 has been marked as a duplicate of this bug. ***
*** Bug 507127 has been marked as a duplicate of this bug. ***
*** Bug 507175 has been marked as a duplicate of this bug. ***
*** Bug 508532 has been marked as a duplicate of this bug. ***
*** Bug 508425 has been marked as a duplicate of this bug. ***
*** Bug 509564 has been marked as a duplicate of this bug. ***
*** Bug 509576 has been marked as a duplicate of this bug. ***
*** Bug 510243 has been marked as a duplicate of this bug. ***
*** Bug 510656 has been marked as a duplicate of this bug. ***
*** Bug 510661 has been marked as a duplicate of this bug. ***
*** Bug 511115 has been marked as a duplicate of this bug. ***
*** Bug 511448 has been marked as a duplicate of this bug. ***
*** Bug 511445 has been marked as a duplicate of this bug. ***
*** Bug 511837 has been marked as a duplicate of this bug. ***
*** Bug 512321 has been marked as a duplicate of this bug. ***
*** Bug 512749 has been marked as a duplicate of this bug. ***
*** Bug 513069 has been marked as a duplicate of this bug. ***
*** Bug 513087 has been marked as a duplicate of this bug. ***
*** Bug 514950 has been marked as a duplicate of this bug. ***
*** Bug 514578 has been marked as a duplicate of this bug. ***
*** Bug 514422 has been marked as a duplicate of this bug. ***
*** Bug 515440 has been marked as a duplicate of this bug. ***
*** Bug 515682 has been marked as a duplicate of this bug. ***
*** Bug 516588 has been marked as a duplicate of this bug. ***
*** Bug 516861 has been marked as a duplicate of this bug. ***
*** Bug 517905 has been marked as a duplicate of this bug. ***
*** Bug 518526 has been marked as a duplicate of this bug. ***
*** Bug 519452 has been marked as a duplicate of this bug. ***
*** Bug 520030 has been marked as a duplicate of this bug. ***
*** Bug 520419 has been marked as a duplicate of this bug. ***
*** Bug 520821 has been marked as a duplicate of this bug. ***
*** Bug 521039 has been marked as a duplicate of this bug. ***
*** Bug 521565 has been marked as a duplicate of this bug. ***
*** Bug 521547 has been marked as a duplicate of this bug. ***
*** Bug 521677 has been marked as a duplicate of this bug. ***
*** Bug 529203 has been marked as a duplicate of this bug. ***
*** Bug 508861 has been marked as a duplicate of this bug. ***