Bug 785628 - [abrt] evolution-3.2.3-1.fc16: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-3.2.3-1.fc16: Process /usr/bin/evolution was killed by signa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4798e2c95f45bf691dd58a839a6...
: 758517 761613 785630 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 04:25 UTC by Mikhail
Modified: 2013-02-13 16:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 16:39:32 UTC
Type: ---


Attachments (Terms of Use)
File: dso_list (24.31 KB, text/plain)
2012-01-30 04:25 UTC, Mikhail
no flags Details
File: gconf_subtree (22.27 KB, text/plain)
2012-01-30 04:25 UTC, Mikhail
no flags Details
File: maps (69.82 KB, text/plain)
2012-01-30 04:25 UTC, Mikhail
no flags Details
File: backtrace (51.94 KB, text/plain)
2012-01-30 04:25 UTC, Mikhail
no flags Details
valgrind log (11.20 KB, text/plain)
2012-01-31 06:11 UTC, Mikhail
no flags Details
yet another valgrind log (13.59 KB, text/plain)
2012-02-02 12:26 UTC, Mikhail
no flags Details
yet another valgrind log 2 (13.79 KB, text/plain)
2012-02-03 04:19 UTC, Mikhail
no flags Details

Description Mikhail 2012-01-30 04:25:04 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        evolution
executable:     /usr/bin/evolution
kernel:         3.2.1-3.fc16.i686.PAE
pid:            26812
pwd:            /home/mikhail
reason:         Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
time:           Вс. 29 янв. 2012 05:57:09
uid:            1000
username:       mikhail
var_log_messages: Jan 29 05:57:26 telecon17l abrt[1373]: Saved core dump of pid 26812 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2012-01-29-05:57:09-26812 (396128256 bytes)
xsession_errors: 

backtrace:      Text file, 53183 bytes
dso_list:       Text file, 24896 bytes
gconf_subtree:  Text file, 22807 bytes
maps:           Text file, 71492 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=telecon17l.afbank.ru
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=dbbbcd64cfc24f5c1bbda6480000000a-1327637478.136187-367742486
:GNOME_KEYRING_CONTROL=/tmp/keyring-b4vuMe
:IMSETTINGS_MODULE=none
:USER=mikhail
:USERNAME=mikhail
:MAIL=/var/spool/mail/mikhail
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/mikhail/.local/bin:/home/mikhail/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/mikhail
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1477
:LANG=en_US.utf8
:GDM_LANG=en_US.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/mikhail
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=mikhail
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-W6rxFKIpQY,guid=02cff8e2a3049214c7fcc0f400000020
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/mikhail
:DISPLAY=:0.0
:XAUTHORITY=/var/run/gdm/auth-for-mikhail-DSpaPv/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1481,unix/unix:/tmp/.ICE-unix/1481
:SSH_AUTH_SOCK=/tmp/keyring-b4vuMe/ssh
:GPG_AGENT_INFO=/tmp/keyring-b4vuMe/gpg:0:1
:LC_TIME=ru_RU.utf8
:LC_NUMERIC=ru_RU.utf8
:LC_MONETARY=ru_RU.utf8
:LC_MEASUREMENT=ru_RU.utf8
:DESKTOP_STARTUP_ID=gnome-panel-1709-telecon17l.afbank.ru-evolution-17_TIME110293668
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/evolution.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=26812

smolt_data:
:
:
:General
:=================================
:UUID: 357b0f0c-1149-42cb-9d0f-3f98b0655a92
:OS: Fedora release 16 (Verne)
:Default run level: Unknown
:Language: en_US.utf8
:Platform: i686
:BogoMIPS: 4788.42
:CPU Vendor: GenuineIntel
:CPU Model: Intel(R) Core(TM)2 Duo CPU     E4600  @ 2.40GHz
:CPU Stepping: 13
:CPU Family: 6
:CPU Model Num: 15
:Number of CPUs: 2
:CPU Speed: 2400
:System Memory: 1968
:System Swap: 4007
:Vendor: Unknown
:System:  
:Form factor: Unknown
:Kernel: 3.2.2-1.fc16.i686.PAE
:SELinux Enabled: 1
:SELinux Policy: targeted
:SELinux Enforce: Enforcing
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:
:
:Devices
:=================================
:(32902:10672:32902:20298) pci, agpgart-intel, HOST/PCI, 82Q35 Express DRAM Controller
:(32902:10544:32902:20298) pci, i801_smbus, SERIAL, 82801I (ICH9 Family) SMBus Controller
:(32902:10530:32902:20298) pci, ahci, STORAGE, 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller
:(32902:10516:32902:20298) pci, None, PCI/ISA, 82801IO (ICH9DO) LPC Interface Controller
:(32902:4285:32902:1) pci, e1000e, ETHERNET, 82566DM-2 Gigabit Network Connection
:(32902:10564:32902:10564) pci, pcieport, PCI/PCI, 82801I (ICH9 Family) PCI Express Port 3
:(32902:9294:32902:20298) pci, None, PCI/PCI, 82801 PCI Bridge
:(32902:10566:32902:10566) pci, pcieport, PCI/PCI, 82801I (ICH9 Family) PCI Express Port 4
:(32902:10549:32902:20298) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI Controller #2
:(32902:10548:32902:20298) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI Controller #1
:(32902:10553:32902:20298) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI Controller #6
:(32902:10550:32902:20298) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI Controller #3
:(32902:10554:32902:20298) pci, ehci_hcd, USB, 82801I (ICH9 Family) USB2 EHCI Controller #1
:(32902:10556:32902:20298) pci, ehci_hcd, USB, 82801I (ICH9 Family) USB2 EHCI Controller #2
:(4523:24833:4523:24833) pci, pata_marvell, STORAGE, 88SE6101/6102 single-port PATA133 interface
:(4545:22545:4545:22545) pci, firewire_ohci, FIREWIRE, FW322/323
:(32902:10674:32902:20298) pci, i915, VIDEO, 82Q35 Express Integrated Graphics Controller
:(32902:10675:32902:20298) pci, None, VIDEO, 82Q35 Express Integrated Graphics Controller
:(32902:10560:32902:10560) pci, pcieport, PCI/PCI, Optiplex 755
:(32902:10562:32902:10562) pci, pcieport, PCI/PCI, 82801I (ICH9 Family) PCI Express Port 2
:(32902:10676:32902:20298) pci, None, SIMPLE, 82Q35 Express MEI Controller
:(32902:10568:32902:10568) pci, pcieport, PCI/PCI, 82801I (ICH9 Family) PCI Express Port 5
:(32902:10558:32902:18) pci, snd_hda_intel, MULTIMEDIA, 82801I (ICH9 Family) HD Audio Controller
:(32902:10551:32902:20298) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI Controller #4
:(32902:10552:32902:20298) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI Controller #5
:
:
:Filesystem Information
:=================================
:device mtpt type bsize frsize blocks bfree bavail file ffree favail
:-------------------------------------------------------------------
:/dev/sda1 / ext4 4096 4096 5112811 2574036 2522850 1286144 1094360 1094360
:

Comment 1 Mikhail 2012-01-30 04:25:09 UTC
Created attachment 558256 [details]
File: dso_list

Comment 2 Mikhail 2012-01-30 04:25:13 UTC
Created attachment 558257 [details]
File: gconf_subtree

Comment 3 Mikhail 2012-01-30 04:25:19 UTC
Created attachment 558258 [details]
File: maps

Comment 4 Mikhail 2012-01-30 04:25:24 UTC
Created attachment 558259 [details]
File: backtrace

Comment 5 Milan Crha 2012-01-30 10:02:10 UTC
Thanks for a bug report. I see in the backtrace that multiple threads reported issues with memory, caused by severe memory corruption. The question is where and why the memory corruption happened. I recall one place, which can cause things like this. It is tracker-evolution-plugin. Do you have this installed, please? Maybe if you disable or uninstall it, then this will be solved. If this is caused by something else, then I'm not aware of any other method than running evolution under valgrind, to let it check the memory operations being done and report any errors it may found. The issue with valgrind is that the process is significantly slower due to all memory checking.

The command looks like this:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
Note that valgrind can avoid certain crashes, it logs about them instead, thus even if the application will not crash then the log can contain the information about the issue. Also make sure that you've installed correct debug information packages at least for gtkhtml3, evolution-data-server, evolution and any other evolution-* packages you are using, thus the log will contained detailed debug information. With 'correct' is meant that the binary package version should be the same as the debuginfo package version, otherwise the symbols doesn't match.

Comment 6 Milan Crha 2012-01-30 10:03:11 UTC
*** Bug 785630 has been marked as a duplicate of this bug. ***

Comment 7 Mikhail 2012-01-31 06:11:24 UTC
Created attachment 558528 [details]
valgrind log

Comment 8 Milan Crha 2012-01-31 08:29:10 UTC
Thanks for the update. Did evolution crash under valgrind too? The log is missing some footer valgrind usually prints, but it also doesn't show the crash itself. The interesting part, from my point of view, is that your MAPI account cannot connect to your server, with an error: NT_STATUS_CONNECTION_REFUSED. Apart of that the log doesn't show any unusal issues from libraries evolution is using, which makes this harder to resolve.

Comment 9 Mikhail 2012-02-02 12:26:47 UTC
Created attachment 559046 [details]
yet another valgrind log

Comment 10 Mikhail 2012-02-02 12:27:45 UTC
Please see yet another valgrind log.

Comment 11 Mikhail 2012-02-03 04:19:58 UTC
Created attachment 559203 [details]
yet another valgrind log 2

Comment 12 Milan Crha 2012-02-03 12:42:46 UTC
Thanks for the update. I'm afraid this cannot be catch by valgrind, neither of those two show any issue I would expect. The second one is quite impressive, because it leaked more than 150MB of memory in not so many blocks. What was the machine doing, just updating? You can add beside --num-callers=50 also parameter --leak-check=full, where the log will contain all such information (the log will be significantly larger). Like I mentioned in comment #5, without debug info packages for evolution-related packages the logs will not be fully usable.

Did you try to disable or uninstall the tracker plugin? You can check when you run evolution from console, it may not mentions Tracker there at all. The valgrind logs you sent above don't have it there mentioned, thus you have it gone probably.

==6101== LEAK SUMMARY:
==6101==    definitely lost: 172,293,627 bytes in 16,831 blocks

Comment 13 abrt-bot 2012-03-30 15:08:53 UTC
Backtrace analysis of bugs across components suggests the actual bug might be in component glib2 instead of component evolution. You might want to inspect the backtraces from the bugs listed below to find out the correct component.

Bugs which were found to be similar to this bug: 
  nautilus: bug #758517
  rhythmbox: bug #761611, bug #761612, bug #761613

This comment is automatically generated.

Comment 14 abrt-bot 2012-03-30 15:09:03 UTC
*** Bug 758517 has been marked as a duplicate of this bug. ***

Comment 15 abrt-bot 2012-03-30 15:09:18 UTC
*** Bug 761613 has been marked as a duplicate of this bug. ***

Comment 16 Fedora End Of Life 2013-01-16 15:17:20 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 17 Fedora End Of Life 2013-02-13 16:39:34 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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