| Summary: | [abrt] evolution-data-server-3.0.2-1.fc15: find_SPropValue_data: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | james.glenn | ||||||||||||||
| Component: | evolution-data-server | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 15 | CC: | mbarnes, mcrha | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | abrt_hash:7033c8219542f3420a9630dc6928469bf432c011 | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2011-06-16 10:09:20 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
james.glenn
2011-06-09 15:13:47 UTC
Created attachment 503921 [details]
File: maps
Created attachment 503922 [details]
File: backtrace
Please let me know if I can provide anything else. Thanks, James Glenn Thanks for a bug report. A similar one had been reported in bug #701955 and is also filled as an upstream bug [1]. The thing is that the bug is not reproducible on my machine, thus I asked, in the upstream bug, for a help with this. If you are able to reproduce this reliable, then it would be great if you could give it a try. I see that this happens when the calendar factory is fetching events from your Exchange server. I would like to ask you to try following steps: a) close evolution, and invoke on a console: evolution --force-shutdown b) remove local cache of events from the exchange server; it is located in $ ~/.cache/evolution/calendar/mapi* All this stuff is stored on the server and the cache serves as a local copy for quicker operations, this it can be removed safely. c) run e-calendar-factory under valgrind, like this: G_SLICE=always-malloc valgrind --num-callers=50 \ /usr/libexec/e-calendar-factory &>log.txt d) finally run evolution from another console, go to calendar and let it fetch all items from the Exchange server. You may see higher CPU usage, due to all memory checking in valgrind. In a case the calendar factory will not crash after full synchronization of events, as valgrind can avoid certain types of crashes, then please use evolution for some time, say half an hour, and then close it. It may close also the e-calendar-factory process after about 10 seconds. If not, then press Ctrl+C in the console you run it, but press it only once. It'll stop valgrind and finish writing into the log.txt file. After this all the log.txt file may contain some useful information, hopefully. It may not contain any private information, like server names, user names or passwords, but check for that, just to be sure. Then upload it here, please. Thanks in advance. [1] https://bugzilla.gnome.org/show_bug.cgi?id=613209 Created attachment 504128 [details]
Log output per request
Created attachment 504129 [details]
Log output per request
Milan, I am able to reproduce this every time I try to load my calendar. Not sure if this is useful information, but I work in a very mixed environment with lots of different clients creating Appointments / Meetings. If you told me that one or more of the Meetings is corrupted some how, I would believe you. Please let me know if you need anything else. Thanks, James Glenn Thanks for the update. This is what I was looking for, it shows memory issues. I would like to ask you for one more update, though, because there are missing line numbers for the crash, thus if you could install debug info packages for samba4, openchange, evolution-data-server, evolution and evolution-mapi, then it'll be very helpful. With line numbers shown I'll be able to identify critical places more easily and I'll be able to provide a test package for you. I do not believe the event on the server is broken as such, it's rather about a usage on evolution-mapi/libmapi side, than about different clients creating events differently. But that's only my personal opinion, the actual code in use can have different opinion ;) Created attachment 504448 [details]
Log output per request with debuginfo packages
Thanks for your help with this.
> at 0xBCA0840: find_SPropValue_data (in /usr/lib64/libmapi-openchange.so.0.9) > by 0xBA30C46: exchange_mapi_util_find_row_propval (in /usr/lib64 > /libexchangemapi-1.0.so.0.0.0) Thanks for the update. Did it install correct debuginfo packages for openchange and evolution-mapi? The updated valgrind doesn't show line numbers from these two, as shown above. The upstream bug (as mentioned in comment #4) has similar valgrind log, unfortunately also without line numbers. Jun 13 08:50:09 Installed: evolution-data-server-debuginfo-3.0.1-1.fc15.x86_64 Jun 13 08:50:11 Installed: openchange-debuginfo-0.9-16.fc15.x86_64 Jun 13 08:50:14 Installed: samba4-debuginfo-4.0.0-25.alpha11.fc15.x86_64 Jun 13 08:50:15 Installed: evolution-mapi-debuginfo-3.0.1-2.fc15.x86_64 Jun 13 08:50:17 Installed: evolution-debuginfo-3.0.1-1.fc15.x86_64 Is it possible I did not start something properly? I just ran through the same steps outlined in comment #4 (https://bugzilla.redhat.com/show_bug.cgi?id=712144#c4). (In reply to comment #11) > Is it possible I did not start something properly? I just ran through the same > steps outlined in comment #4 I do not think so. The current evolution is 3.0.2, whereas your debuginfo is for 3.0.1, similar for openchange, the current is 0.9-17, where you've debug info for 0.9-16. Samba version is correct, I'm only wondering whether it requires samba4-libs-debuginfo instead. I'm never sure with samba4 packages. Anyway, I believe you did an update and the update didn't take in correct debuginfo packages. It does that from time to time, I noticed that myself some time ago too. I'm not sure why, maybe because the debuginfo repository is usually disabled. Try this command as root, please: $ yum --enablerepo=fedora-debuginfo --enablerepo=updates-debuginfo update Created attachment 504878 [details]
Log output per request with debuginfo packages
Now with line numbers.
Thanks for the update. I see it's basically the same as the upstream bug [1], (also mentioned in comment #4), thus please let's move there. [1] https://bugzilla.gnome.org/show_bug.cgi?id=613209 |