Bug 663776
| Summary: | [abrt] evolution-2.28.3-10.el6: ORBit_RootObject_duplicate: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Marc Milgram <mmilgram> | ||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | desktop-bugs <desktop-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.0 | CC: | jhunt, mcrha | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:c9321574c0d35af888850a6565c41421e55886a1 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-01-17 15:17:13 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Marc Milgram
2010-12-16 19:45:27 UTC
Created attachment 469206 [details]
File: backtrace
Thanks for a bug report. I believe this happened just as you described, the calendar, when unchecked, didn't clear all parts of it, namely the ORBit part, thus when it received asynchronous reply about new objects added, then it was operating on already freed memory (the 0xaaaaaaaaaaaaa pointer). Maybe there is missing some signal disconnection, though the question is where there, because in the below backtrace is only the very bottom, the main.c, part from evolution, the rest is from other libraries.
#0 0x000000301c62edb0 in ORBit_RootObject_duplicate (obj=0xaaaaaaaaaaaaaaaa)
at orbit-object.c:125
#1 0x000000301c63fcbf in ORBit_POAObject_handle_request (
pobj=0x7f8b980061b0, opname=0x7f8bb80398bc "notifyObjectsAdded",
ret=<value optimized out>, args=<value optimized out>, ctx=0x0,
recv_buffer=0x7f8bb800aa40, ev=<value optimized out>) at poa.c:1228
#2 0x000000301c6404a1 in ORBit_POAObject_invoke_incoming_request (
pobj=0x7f8b980061b0, recv_buffer=0x7f8bb800aa40, opt_ev=0x0) at poa.c:1427
#3 0x000000301c6292cc in giop_thread_queue_process (tdata=0x1d12280)
at giop.c:792
#4 0x000000301c629458 in giop_mainloop_handle_input (
source=<value optimized out>, condition=<value optimized out>,
data=<value optimized out>) at giop.c:482
#5 0x0000003013a38f0e in g_main_dispatch (context=0x1ce93f0) at gmain.c:1960
#6 IA__g_main_context_dispatch (context=0x1ce93f0) at gmain.c:2513
#7 0x0000003013a3c938 in g_main_context_iterate (context=0x1ce93f0, block=1,
dispatch=1, self=<value optimized out>) at gmain.c:2591
#8 0x0000003013a3cd55 in IA__g_main_loop_run (loop=0x1d59ff0) at gmain.c:2799
#9 0x0000003024e2d106 in bonobo_main () at bonobo-main.c:311
#10 0x000000000041569a in main (...) at main.c:732
Package: evolution-2.28.3-10.el6 Architecture: x86_64 OS Release: Red Hat Enterprise Linux Workstation release 6.0 (Santiago) How to reproduce ----- 1. Evolution was left open for a couple of hours and when I clicked in the main window, the entire application crashed . Comment ----- evolution-2.28.3-10.el6.x86_64 evolution-data-server-devel-2.28.3-10.el6.x86_64 evolution-data-server-debuginfo-2.28.3-10.el6.x86_64 evolution-mapi-0.28.3-6.el6.x86_64 evolution-data-server-2.28.3-10.el6.x86_64 evolution-data-server-doc-2.28.3-10.el6.noarch evolution-help-2.28.3-10.el6.noarch I'm thinking how much this is related to the upstream bug [1]. I'll try to reproduce it here and see what I'll find. [1] https://bugzilla.gnome.org/show_bug.cgi?id=627788 *** Bug 669761 has been marked as a duplicate of this bug. *** (In reply to comment #6) > I'm thinking how much this is related to the upstream bug [1]. I'll try to > reproduce it here and see what I'll find. > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=627788 Ouch, my fault, I'm sorry, this is related to bug #660356, it's the same issue, only other place of the crash, few steps earlier than in that bug. I'm marking this as a duplicate of that bug. *** This bug has been marked as a duplicate of bug 660356 *** |