Bug 861065 - [abrt] evolution-3.5.92-2.fc18: g_closure_unref: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
[abrt] evolution-3.5.92-2.fc18: g_closure_unref: Process /usr/bin/evolution w...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
18
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
abrt_hash:02d8996398af84085aa619e4162...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-27 08:59 EDT by Mark van Rossum
Modified: 2012-10-16 08:13 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-10-16 08:13:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: core_backtrace (10.01 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: environ (3.18 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: limits (1.29 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: backtrace (67.55 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: cgroup (130 bytes, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: maps (133.92 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: dso_list (28.86 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: build_ids (10.65 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: open_fds (2.64 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details
File: var_log_messages (1.50 KB, text/plain)
2012-09-27 08:59 EDT, Mark van Rossum
no flags Details

  None (edit)
Description Mark van Rossum 2012-09-27 08:59:33 EDT
Description of problem:
random crash

Version-Release number of selected component:
evolution-3.5.92-2.fc18

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
backtrace_rating: 4
cmdline:        evolution
crash_function: g_closure_unref
kernel:         3.6.0-0.rc7.git0.1.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #6 g_closure_unref at gclosure.c:601
: #7 handler_unref_R at gsignal.c:645
: #8 g_signal_handler_disconnect at gsignal.c:2573
: #9 weak_unbind at gbinding.c:243
: #10 weak_refs_notify at gobject.c:2469
: #12 gtk_notebook_forall at gtknotebook.c:4482
: #13 gtk_container_destroy at gtkcontainer.c:1377
: #18 gtk_widget_dispose at gtkwidget.c:10265
: #20 gtk_paned_forall at gtkpaned.c:1956
: #21 gtk_container_destroy at gtkcontainer.c:1377
Comment 1 Mark van Rossum 2012-09-27 08:59:36 EDT
Created attachment 618036 [details]
File: core_backtrace
Comment 2 Mark van Rossum 2012-09-27 08:59:38 EDT
Created attachment 618037 [details]
File: environ
Comment 3 Mark van Rossum 2012-09-27 08:59:40 EDT
Created attachment 618038 [details]
File: limits
Comment 4 Mark van Rossum 2012-09-27 08:59:42 EDT
Created attachment 618039 [details]
File: backtrace
Comment 5 Mark van Rossum 2012-09-27 08:59:44 EDT
Created attachment 618040 [details]
File: cgroup
Comment 6 Mark van Rossum 2012-09-27 08:59:46 EDT
Created attachment 618041 [details]
File: maps
Comment 7 Mark van Rossum 2012-09-27 08:59:48 EDT
Created attachment 618042 [details]
File: dso_list
Comment 8 Mark van Rossum 2012-09-27 08:59:50 EDT
Created attachment 618043 [details]
File: build_ids
Comment 9 Mark van Rossum 2012-09-27 08:59:52 EDT
Created attachment 618044 [details]
File: open_fds
Comment 10 Mark van Rossum 2012-09-27 08:59:54 EDT
Created attachment 618045 [details]
File: var_log_messages
Comment 11 Milan Crha 2012-10-16 08:13:08 EDT
Thanks for a bug report. The crash comes from gtk, somewhere deep in gtk while destroying some widget, probably a dialogue or window. As it;'s a memory corruption bug, it could happen basically anywhere, thus it would be good to try to find a reproducer steps, though I agree it's quite hard for memory corruption bugs. I'm closing this for now, but if you'll manage to reproduce this with some steps, then it'll be highly appreciated.

Note You need to log in before you can comment on or make changes to this bug.